Develop Bugs

How I can apply Security Patches on a Rooted Rom?

Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?

If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there

Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.

Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.

How to block OTA? Rooted

Hi,
Normally I'd search but as this is a non Nexus I am going to be cautious and patient. I would like to know how to block any OTA. I am rooted with TWRP flashed and I'm happy on M with xposed. I've had N and I'm in no rush for the bugs and whatnot and I'd rather keep xposed.
So for the Moto z play what is the best way to block OTA updates, and how would it be reverted, should I ever care about N.
Thanks in advance.

You may try DisableService, it should help.
Edit: Guess the right one is "Motorola Updateservices" on System Tab

darkrom said:
Hi,
Normally I'd search but as this is a non Nexus I am going to be cautious and patient. I would like to know how to block any OTA. I am rooted with TWRP flashed and I'm happy on M with xposed. I've had N and I'm in no rush for the bugs and whatnot and I'd rather keep xposed.
So for the Moto z play what is the best way to block OTA updates, and how would it be reverted, should I ever care about N.
Thanks in advance.
Click to expand...
Click to collapse
Or flash my stock ROM found in the development threads , I removed 3 ota APK from priv/apps
Sent from my XT1635-02 using XDA-Developers Legacy app

darkrom said:
Hi,
Normally I'd search but as this is a non Nexus I am going to be cautious and patient. I would like to know how to block any OTA. I am rooted with TWRP flashed and I'm happy on M with xposed. I've had N and I'm in no rush for the bugs and whatnot...
Click to expand...
Click to collapse
Lol
This forum is crazy chomping at the bit for 7.0 and not 7.11.
I have stopped the Update without root.

If you have any kind of modification on your software, be it root or TWRP, you don't have to stop anything since the OTA will not install at all, even if you wanted to. You have to go back to full stock to install any official OTAs.

flashallthetime said:
Or flash my stock ROM found in the development threads , I removed 3 ota APK from priv/apps
Click to expand...
Click to collapse
You missed the part about re-enable OTA. Just disabling the service is easy to enable again. For your idea: Take a Nandroid backup of boot, system and recovery and restore if OTA wanted?
Just an addition: It's not always easy to fulfill the conditions for OTA when rooted. Mainly: Original recovery. No whatsoever modification of /system (AdAway, Xposed, build.prop etc​.). And if I'm right informed, it fails if you undo some modification, because it works on blocks, not file based.

tag68 said:
You missed the part about re-enable OTA. Just disabling the service is easy to enable again. For your idea: Take a Nandroid backup of boot, system and recovery and restore if OTA wanted?
Just an addition: It's not always easy to fulfill the conditions for OTA when rooted. Mainly: Original recovery. No whatsoever modification of /system (AdAway, Xposed, build.prop etc​.). And if I'm right informed, it fails if you undo some modification, because it works on blocks, not file based.
Click to expand...
Click to collapse
Didn't read or see that part.
Unfortunately the way to restore your system to stock is you'll have to flash all the sparsechunks, recovery, boot.img and the OEM.img.
May probably can just leave your data alone .
Just a note, as soon as nougat drops and I get my hands on the firmware, I'll be hopefully building a stock nougat ROM.
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
Unfortunately the way to restore your system to stock is you'll have to flash all the sparsechunks, recovery, boot.img and the OEM.img.
Click to expand...
Click to collapse
If Xposed is installed without Magisk, and twrp flashed, this is the way to go anyway.
flashallthetime said:
May probably can just leave your data alone .
Click to expand...
Click to collapse
You can. Did this several times. Flashed July (August?) security ROM, update September and October, try flash Magisk, restore Nandroid boot, recovery and system - not working, start over. After updates flash Magisk and phh superuser, working fine. All this without change to data. Of course this only works if you stay on compatible ROM. Probably it should be stock or at least some only slightly modified.

Is there an easy way to update an unlocked/rooted Pixel 3a XL?

I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom

Tom2112 said:
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Click to expand...
Click to collapse
I have seen postings about people fastboot flashing back the original boot.img, then taking the ota then repatching the new boot image and flashing it via fastboot. Not as simple as you hoped i am sure but it works.
The other way is to download the full image, remove the -w option in the flashsall.bat and then run the modded flashall file. You then need to patch the new boot image as above and fastboot flash that to regain root. I have not found any other ways to get updates besides doing one of the 2 above every month

Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.

Tom2112 said:
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Click to expand...
Click to collapse
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Sideloading the ota would be a great option EXCEPT he said he was on a much older version... Like sept.
My understanding is that the ota for dec would only contain changes implemented for the month of December, this in this scenerio he would not get the patches for October and November with your method and i am not even sure if it would boot after that mismatch
It's really not saving much work if any over flashing the full version, and with the full version they're is no potential for bootloop due to missing some patches or updates. It's just much safer.

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?

Tom2112 said:
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Click to expand...
Click to collapse
https://developers.google.com/android/ota

The most simple way to update while keeping root would be to follow the instructions for "Devices with A/B Partitions" at the following link in the Magisk documentation:
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Basically, Magisk allows you to restore the original boot image to the current partition so you can take the OTA when it arrives on your phone. Before rebooting you install Magisk to the inactive slot so that when the phone restarts you retain root without having to mess with Fastboot.

Delete Me!
Think all you have to do is click uninstall magisk, dont reboot... Take ota, but before reboot click install magisk/ install to empty slot...
Oops didnt see the reply above

OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?

Tom2112 said:
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Click to expand...
Click to collapse
This should be a one time issue. One of the latest versions of Magisk changed the default location of the boot.img backup. They released it in December after most of us had already upgraded to the December Pixel update. This means we used the older version of Magisk when we installed the Dec update and it saved the backup to the old/original location. We then updated Magisk sometime later in December, but the Magisk update doesn't move the backup file to the new location (a poor execution from the Magisk team IMHO). Because we are now on the updated version, it expects the boot.img backup to be in the new location, but it is still in the old location and Magisk doesn't check that old location (again, a poor execution from the Magisk team IMHO).
To fix this you have several options.....
Option one is to find the original backup location that Magisk used for the boot.img and move it to the new backup location that Magisk uses. Unfortunately, I don't know where those backup locations are and didn't feel like researching it, so I used one of the other methods.
Option two is to "reinstall" Magisk (choose the patch file option and select the stock boot.img that may still on the phone from whatever the last update was (if you sideloaded the update and then had to rerooted the phone)- or download it from the applicable factory image and move it to the phone) to force Magisk to backup the current boot.img file to the new location. Stop after this initial step (ie you don't actually need to flash the patched file because it has already been done). Then you should be able to follow the normal Magisk update process to move to the January update.
That being said, I have horrible success being able to take the updates OTA (they usually fail) and usually end up sideloading the update. That is the final option - sideload the Jan update and then reroot the phone using the normal root method (ie getting Magisk to patch the stock boot.img file and then flashing the patched file).

Question OTA OOS 1.2.3.3 AA Boot Image Needed

Just curious if anybody has been able to get the boot image from the incremental update of OOS 1.2.3.3 AA from Magisk ?
I recently got the boot image for 1.2.2 AA from someone using magisk so just wondering if anybody has gotten the latest.

oos 11.2.3.3 AA boot.img，you can patch it in magisk 22.0, then flash it via fastboot.

xls654 said:
oos 11.2.3.3 AA boot.img，you can patch it in magisk 22.0, then flash it via fastboot.
Click to expand...
Click to collapse
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website

Andrew8578 said:
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Click to expand...
Click to collapse
Im pretty sure he was able to get it through magisk and installing an inactive slot to the latest OOS. and then got the stock boot image of 1.2.3.3 but i could be wrong lol

For what it is worth, I ended up not needing this, this time. I was able to use Magisk's Uninstall/Restore function and install the OTA. This OTA did not force a reboot, so I was able to go back into Magisk and reinstall to active and inactive slots before rebooting and all was good.

dmarden said:
For what it is worth, I ended up not needing this, this time. I was able to use Magisk's Uninstall/Restore function and install the OTA. This OTA did not force a reboot, so I was able to go back into Magisk and reinstall to active and inactive slots before rebooting and all was good.
Click to expand...
Click to collapse
I did something similar, which is to restore the image in magisk manager, which requires a reboot to take effect. And after rebooting, I lost root, however, the update worked.
How am I suppose to reinstall magisk after that?

Andrew8578 said:
I did something similar, which is to restore the image in magisk manager, which requires a reboot to take effect. And after rebooting, I lost root, however, the update worked.
How am I suppose to reinstall magisk after that?
Click to expand...
Click to collapse
You do not need to reboot after the restore.

dmarden said:
You do not need to reboot after the restore.
Click to expand...
Click to collapse
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method

Andrew8578 said:
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Click to expand...
Click to collapse
Yeah this happened to me.
All you have to do is update to the latest os and then download the boot image that's in this post and then go into magisk
And select file and patch
then move it to your pc
flash the patched boot image.
and then go into magisk and direct install

wooo000 said:
Yeah this happened to me.
All you have to do is update to the latest os and then download the boot image that's in this post and then go into magisk
And select file and patch
then move it to your pc
flash the patched boot image.
and then go into magisk and direct install
Click to expand...
Click to collapse
Yes, the image provided sure works. But I want to figure out how you can get the boot image yourself.
I tried to set my active slot to the inactive one, but I get nothing and it just reboot to the previous slot after a while.

Andrew8578 said:
I did not know that. That is good to know.
Did you just restore the image, install the update, and then reinstall magisk with the OTA feature? or did you use another method
Click to expand...
Click to collapse
Something is weird with the process this time, IMO... so after the OTA installs, I use Magisk to install to both the current and inactive slot.

Great information and useful site.

Hey guys, just to be sure.
Would I be on the right track for installing OTA 11.2.3.3LE15AA on 11.2.2.2LE15AA OP9P AA:
Place OTA 11.2.3.3LE15AA on root storage
Fastboot boot 11.2.3.3 "Root lost"
Install local upgrade of OTA 11.2.3.3LE15AA no reboot
Magisk patch Direct Install then Magisk patch inactive slot, reboot.
Can anyone let me know.
Tx guys!

My question is how did someone get the boot.img from the OTA 11.2.3.3AA? I tried 3 different payload dumper and none extract the images.

schmeggy929 said:
My question is how did someone get the boot.img from the OTA 11.2.3.3AA? I tried 3 different payload dumper and none extract the images.
Click to expand...
Click to collapse
Get the full update zip from Oxygen updater and patch that.

Droidzone said:
Get the full update zip from Oxygen updater and patch that.
Click to expand...
Click to collapse
I know that, I'm talking about the incremental OTA. The incremental OTA 11.2.3.3 AA is out. The full OTA isn't, how did someone pull the boot.img from the incremental OTA?

Andrew8578 said:
how did you get the image? You lose root after updating, since you need a stock boot image to update, and global is not updated on the website
Click to expand...
Click to collapse
I coyped it from magisk backup, before incremental OTA reboot, At that time I still in rooted

xls654 said:
I coyped it from magisk backup, before incremental OTA reboot, At that time I still in rooted
Click to expand...
Click to collapse
that makes sense actually. It's still weird that you don't need to reboot to get the boot image. But i'll keep that in mind. Thank you!

Question Update and Magisk Root

How do I update my Magisk Rooted oneplus 9 pro without losing root access?

Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit

I found oxygen updater in Google play store. Is that what you're talking about?

sbcdave said:
I found oxygen updater in Google play store. Is that what you're talking about?
Click to expand...
Click to collapse
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro

Shanemichealrowland said:
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Click to expand...
Click to collapse
Yes it does, I've been using it since I got my op9pro on 1st April.

thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.

Bunecarera said:
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Click to expand...
Click to collapse
I assume you disable all magisk modules prior updating.

netgar said:
I assume you disable all magisk modules prior updating.
Click to expand...
Click to collapse
Yes.

There are no full ota's for LE2125 Global 11.2.5.5 AA yet!

galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA
Click to expand...
Click to collapse
This is rather annoying. Why are we left behind?

the bolt of thunder said:
This is rather annoying. Why are we left behind?
Click to expand...
Click to collapse
I think it's because the Global ota's are being stored on Google servers instead of the OnePlus servers for some reason

Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
I updated my BA using oxygen updater (download full os, settings/system/system updates/lokal update) without touching magisk at all. reboot, bootloader, reflash https://mega.nz/file/bNozXKJI#0zNfKtRw1IBqG6ojFuW3830dxXLgewmtsbbh4T4WGzs (I know its 1.1.2.4.4, but it works...) done

Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.

dreinulldrei said:
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
Click to expand...
Click to collapse
thats what i did first of all, my device didnt boot at all but kept going to stock recovery. afterwards i flashed what i wrote above, everythinx fine now.

galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
Click to expand...
Click to collapse
I decided to unroot and take the update. I'll just wait until the full OTA comes to us before rooting. :/

thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..

Flying Fox said:
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Click to expand...
Click to collapse
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.

There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.

dreinulldrei said:
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
Click to expand...
Click to collapse
schmeggy929 said:
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
Click to expand...
Click to collapse
Thx for your answers!! Nice to be back to Oneplus. Great community here...

Does anyone know if oxygen updater from the play store is a trustworthy source for these OTAs?