I want to update my Pixel phone with the latest monthly update, but also install Magisk and Xposed. But I want to do this without rebooting so that Xposed is always working.
How do I do this?
Is Flashfire the best way to do this, or can I do this manually.
I used to update my Nexus5 by downloading the full monthly update, opening the zip on my PC and then flashing the system update before booting into TWRP to apply Xposed.
But how do I do this on a pixel with the A/B partitions and the like.
Any help would be appreciated.
Ta.
scutworker said:
I want to update my Pixel phone with the latest monthly update, but also install Magisk and Xposed. But I want to do this without rebooting so that Xposed is always working.
How do I do this?
Is Flashfire the best way to do this, or can I do this manually.
I used to update my Nexus5 by downloading the full monthly update, opening the zip on my PC and then flashing the system update before booting into TWRP to apply Xposed.
But how do I do this on a pixel with the A/B partitions and the like.
Any help would be appreciated.
Ta.
Click to expand...
Click to collapse
I could be wrong but I don't think flashfire works with magisk but essentially no there is no way to do what it is you want. You could manually flash the factory images and re-mod or wait for a custom kernel you like to integrate latest security patches and flash that.
KittyRgnarok said:
I could be wrong but I don't think flashfire works with magisk but essentially no there is no way to do what it is you want. You could manually flash the factory images and re-mod or wait for a custom kernel you like to integrate latest security patches and flash that.
Click to expand...
Click to collapse
Thanks.
So is it just a case of boot to bootloader, manually flashing the factory image, then boot TWRP and flash Magisk and Xposed?
Ta.
scutworker said:
Thanks.
So is it just a case of boot to bootloader, manually flashing the factory image, then boot TWRP and flash Magisk and Xposed?
Ta.
Click to expand...
Click to collapse
Yep. You can also remove the -w in the flash-all.sh file so you can keep your data. (Or flash-all.bat if on windows)
Related
Hello XDA!
It's been a while since I did 'modding' on phones, I think I started with the OP1 back in 2014 but have not really been keeping up ever since. I am now on 5.1.5 and running official OOS with magisk and xposed for gravitybox.. Can I just disable magisk and xposed, do the OTA update and then re-enable or do I have to uninstall them fully? Or can I just do the OTA right now?
Sorry for what might be a really obvious answer.
Thank you!
You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process
Hitman478™ said:
You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process
Click to expand...
Click to collapse
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!
maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
This will useful only if don't have TWRP, in other case you'll lose twrp in this way
---------- Post added at 15:21 ---------- Previous post was at 15:19 ----------
TheHighLife said:
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!
Click to expand...
Click to collapse
TWRP official has no bug, the only thing i don't know is if backup/restore is working fine, if you install ota via TWRP and then flash (without reboot) twrp.zip and magisk, after reboot you'll find out that system is exactly the same it was before updating
The only thing u need to disable before updates are overlays through substratum, I also remove any security like finger prints, face unlock and pin or patterns too just in case. Once u flash update u will have to reflash magisk and xposed too
trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
Did anyone try this?
defsix said:
Did anyone try this?
Click to expand...
Click to collapse
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery
trivita said:
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery
Click to expand...
Click to collapse
Same as that. I'll give it a try next update.
Sent from my Brain using my Keyboard
How do you install to second partition? I only get install or uninstall Magisk (16.70) on the screen. i AM NEW TO MAGISK.
My phone keeps bugging me to upgrade to Android 10. I have systemless root, magisk etc.
Is this safe to just do? Do I need to get the image from elsewhere and start over? I've had an update alert come through from Magisk announcing Android 10 compatibility, so I'm guessing that won't be an issue...
I really only wander in here whenever I get a new phone so I have no clue how this works.
you can update to android 10 just fine with magisk installed, however you will lose it once the upgrade is done. you will need to patch your boot image with magisk once you are on android 10.
Not sure what that means.
koberulz said:
Not sure what that means.
Click to expand...
Click to collapse
You. Will. Need. To. Patch. Your. Boot. Image. With. Magisk. After. You. Update. To. Android. 10.
I can read, dude.
What's a boot image? How do I patch it? What are the actual steps here?
koberulz said:
I can read, dude.
What's a boot image? How do I patch it? What are the actual steps here?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
So start the root process over, basically? Is there any point in doing the OTA update or do I just grab the latest image from the website?
Steps 7/8 say there's no TWRP for Android 10 yet, so how does that work?
koberulz said:
So start the root process over, basically? Is there any point in doing the OTA update or do I just grab the latest image from the website?
Steps 7/8 say there's no TWRP for Android 10 yet, so how does that work?
Click to expand...
Click to collapse
you can not install twrp on android 10, you can still boot twrp though. you will not need twrp for the boot image patch.
update your phone to android 10, get the boot.img from the factory image of the version you updated to, using magisk manager patch that boot.img, boot to bootloader, flash the patched boot.img with
Code:
fastboot flash boot_a patchedboot.img
and
Code:
fastboot flash boot_b patchedboot.img
(or only flash for the boot of the current slot you are on, doesnt really matter)
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Flipz77 said:
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Click to expand...
Click to collapse
i usually do this also
Flipz77 said:
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Click to expand...
Click to collapse
There are monthly updates?
I've not been aware of anything at all until now, because now it's sending me a notification.
koberulz said:
There are monthly updates?
I've not been aware of anything at all until now, because now it's sending me a notification.
Click to expand...
Click to collapse
December will be the last one, sadly
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
+1
Sent from my Pixel 3 using Tapatalk
adrianppa said:
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
Click to expand...
Click to collapse
AFAIK, your only choices are to sideload the OTA from https://developers.google.com/android/ota and re-root. You can also flash the factory image and re-root. Be sure to remove the -w from flash-all.bat/sh so you don't wipe your data. I prefer the factory image method. You can patch boot.img before flashing the image, which makes re-rooting a bit easier. I believe there have been some reports of OTA working again after flashing the factory image.
well you have root duh lol, off course otas will fail, at least they dont install unlike old times when install would be error
there are many ways to install but this is the easiest for me every month
each month download full system image
copy boot to phone and patch it with magisk apk, copy back to pc
apply full system image flash all.bat but remove the -w from the .bat (Edit the bat)
this will install the lastest ota but you wont lose any data or settings, everything well be okay
root is lost, now you have to root again
boot magisk boot image
apply direct install in magisk apk
restart
this has to be done every month
you can also uninstall magisk every month and let the ota download and install but that is even slower and annoying, this is how is done
Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,