Related
What You'll Need:
The experimental firmware: https://androidfilehost.com/?fid=745425885120704448 (Thanks @NavSad !)
My updated G900A RootPack: https://drive.google.com/file/d/1U7vwyq4T4609SiUQz43zLXvYOu9Hqohb/view?usp=sharing
(Windows Defender may detect TowelRoot as an Android Malware Exploit, you may need to disable defender temporarily.)
If you want to downgrade to NCE/KitKat: The G900A_NCE.Zip file: https://drive.google.com/file/d/1ahpVGnG3bQ-mEoztN4XUvdbTOW64IdoT/view?usp=sharing
Get Ready:
You will need to extract the RootPack files and move the RootPack folder along with the G900A_Firmware.zip to an external SD and put it in your phone.
What To Do:
Step 1: Go back down!
Download the experimental firmware and extract the zip on your computer.
Open Odin3, select the AP slot, and specify the experimental firmware so you can flash it.
Under Options, Make sure only "AutoReboot" and "F. Time Reset" are selected.
FLASH
Step 2: Our Old Friend
After the OS is installed, go to the file manager and install Flashfire, SuperSU, TowelRoot, BusyBox, and SafeStrap.
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Now open the SuperSU app and hit "continue", let it do its thing and then update the SU binaries (you don't have to reboot)
Step 3. Where to go?
You now need to determine where you want to go?
You can downgrade to NCE or upgrade to OF3
NCE DOWNGRADE/ROOT GUIDE
(KitKat) (Will downgrade you to KitKat and root it)
Now open BusyBox, dismiss the social prompt, and hit install
Now open SafeStrap Installer, grant SU Permissions, and Install recovery (DO NOT Reboot into it)
Open FlashFire, Grant SU Permission, and Accept the Disclaimer.
Hit the '+' and hit 'Flash Firmware Package', navigate and select the G900A_NCE.Zip, and let it scan the archive.
Check Recovery, System, Cache, and Persist. Uncheck modem/Firmware
Hit the Check in the Top Right to confirm changes and Hit the '+' again
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag wipe above the flash firmware package
Select EverRoot, Uncheck "Inject SuperSU" (If you don't, it will cause a kernel panic)
Select Reboot, Check Select "Preserve Recovery", and select the check in the top right to confirm changes (If you don't do this, you won't have recovery once you downgrade.)
HIT FLASH and OK (This will work, don't panic) It may take up to five minutes for the process to complete, if it fails, reflash combination.
After the OS is installed, go to the file manager and install TowelRoot, SuperSU, BusyBox, And SafeStrap
Run towelroot. Simply hit "make it ra1n" and 3 seconds later you'll have the root binaries installed.
Reboot to make SuperSU detect root.
Now open the SuperSU app and hit "continue", let it do its thing and then update the SU binaries (Yes, Reboot now)
Now open BusyBox, grant SU Permissions, dismiss the inital message and install busybox
Now open SafeStrap, grant SU Permissions, Install Recovery.
Your all set.
OF3 UP/DOWNGRADE/ROOT GUIDE
(Lollipop) (Will downgrade you to Lollipop and root it)
Open FlashFire, Grant SU Permission, and Accept the Disclaimer.
Select "Flash Zip/OTA" and Select the G900A_OF3.zip
Mount /system read/write
Select "Flash Zip/OTA" and Select the G900A_OF3_Tether.zip
Mount /system read/write
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag wipe above the flash firmware package (This will fix battery/heating/lag issues while your on OF3) (Trust Me)
Select Wipe System. 3rd Party Apps, Cache Partition, Cache Partition Format, and select the check in the top right to confirm changes
Drag below the G900A_OF3.zip (This will clean up the setup) (Trust me)
Hit "flash", let it flash, reboot, and load.
HIT FLASH and OK
After OS is installed, you will have root.
Copy G900A_OF3_Kernel.zip to the RootPack folder.
Install BusyBox, open and grant SU, Install BusyBox
Install SafeStrap, open and grant SU, Install to Recovery. (DO NOT Reboot into it)
Download the NCE_Flasher then install it, and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish or even ANOTHER ROM, just make sure you wipe everything but the external SD card if you are flashing a new ROM and you should be good.
Remember to ReFlash the G900A_OF3_Kernel.zip file in SafeStrap before you exit SafeStrap otherwise you will not be able to reboot.
If you forget and end up with an error, Just flash G900A_OF3_Kernel.zip with Odin3. (It won't wipe anything)
Marshmallow
---Working on a method---
(Won't stop until I have every update rooted.)
Marshmallow is currently unrootable on the G900A and G900V (CID 11). A method will likely appear in the future.
It is safe for you to flash to the latest Marshmallow, you will be able to restore the experimental combination to root again.
Notes: This guide is an updated version of AptLogic's Guide. ( Can a mod please sticky that thread )
I have created this thread as an "elimination of confusion"/"Catch All" and I will update the thread once I get root on Marshmallow , https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196.
Thank you to AptLogic and everyone involved in the development of root for this device.
Which File where?
So which files go in which slots in ODIN ?
NM...I get it now. Thanks will let you know how it worked for me !
CheeseMerchant said:
So which files go in which slots in ODIN ?
NM...I get it now. Thanks will let you know how it worked for me !
Click to expand...
Click to collapse
Guide Updated.
Works Great !
Justin1198 said:
Guide Updated.
Click to expand...
Click to collapse
Thank you !!! This worked great!
It has not worked for me or something I did wrong
please help me
Since I can downgrade my S5 to kitkat does that mean that I can use the CyanogenMod build for kitkat on the s5 or will it brick my phone ?
First off, thank you so much for this guide! I recently got an old Galaxy S5 from my Dad, and rolled it back to KitKat using these instructions.
I'm experiencing two rather strange issues, though.
1) KitKat doesn't seem to be remembering my Wi-Fi password. I'm having to re-enter it every time I reboot the phone.
2) I'm getting a message on booting that "Safestrap is disabled. System will start in 10 seconds." The system starts like it should, but this message pops up every time. Is this normal, or will something correct it?
Any assistance would be appreciated. Thanks!
The Google Drive links are dead. Could we get new ones please @Justin1198?
Thanks in advance!
If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.
Perfect manual and working great
gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!
Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?
Yes if you are offered the aa rom in the updater
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk
SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.
hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.
The 1+ updater has a setting to auto download updates or not. You can change it.
If we have TWRP installed could we get a guide for using the updater app?
kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!
kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).
i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).
Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)
Hey everyone, sorry if this has been covered already but I don't recall seeing these instructions anywhere. After doing the standard tethered re-root every time there was an OTA update I discovered that you don't need to tether. I've been doing it this way for the past several updates and it has worked perfectly every time. Not sure if this will work for major version updates though. As usual, YMMV, back up your data, I'm not responsible for data loss, bricks, etc. etc.
Install TWRP and Magisk the usual tethered way the first time you root. There's no way around this.
When an OTA update comes out, allow it to download but do not let it install itself.
Download the latest TWRP Fajita zip to your device if you don't already have it. https://dl.twrp.me/fajita/
Reboot to recovery and decrypt if necessary.
Back up your data if you don't feel like living on the edge.
Hit the install button and browse to /sdcard/.Ota and select the latest zip, which was downloaded automatically earlier.
Tap the button to add another zip, and select the TWRP zip that you downloaded earlier.
Swipe to install, reboot when done. It is crucial to install both zips without rebooting in between, otherwise you'll have to tether.
After the post-boot update process completes, open the Magisk Manager app and hit the Install button for Magisk (not Magisk Manager). Choose to download zip only.
Reboot to recovery and decrypt if necessary.
Hit the install button and browse to /sdcard/Download and select the Magisk zip that you just downloaded. Swipe to install, then reboot.
Magisk app should now show Magisk is installed again.
Profit.
If we have twrp retention script we simply can retain magisk and twrp, i think everyone knows that
what is the twrp retention script? have you a link?
Google has changed the way they push and apply OTA updates via GMS, and thus making Magisk Manager's "Install to Inactive Slot" feature bootlooping Pixels. I think I'll hide this option temporarily in the next release before I have time to figure it out (topjohwu)
https://twitter.com/topjohnwu
[Guide] How-to OTA update without loosing Root - Stuck in "Preparing system update"
Hello All, here is a quick guite to avoid getting stuck in "Preparing system update", if you forget to disable automatic system updates you will need to sideload...
The difference between this guide and others is to restore boot images BEFORE checking for updates
1. Make sure automatic system updates are disabled - THIS IS A MUST
Open Settings -> System -> Developer options
Disable 'Automatic system updates'
2. Open to Magisk
Click on UNINSTALL in the bottom
Click on RESTORE IMAGES (You will see Restoration done!)
Once done, DO NOT reboot
3. Now search for System Updates
Go to Settings -> System -> System update
Press 'Download and Install'
Once done, DO NOT reboot
4. Open to Magisk
Click on INSTALL button (for 'Magisk is up-to-date' option)
Press 'Install' again (in the popup)
Press 'Install To Inactive Slot (After OTA)'
Once done, reboot
Please keep in mind that if google detects Magisk (you will get stuck in preparing system update and then no updates will be found), you will need to sideload ota, and re-root your device, to use this guide.
This works on pixel 3, pixel 3XL. pixel 4XL as well
Awesome, I did not know that restoring images would make OTA updates show up!
Hey Guys,
I don't found any similar thread about this topic, so I will create a new.
I have magisk installed and used OxygenOS 12.1 A.10. Today I got the first update to A.12. I did it the same way as I did on Android 11. Recover Image -> Download OTA -> Install OTA -> Install to inactive Slot in magisk.
But on Android 12 it downloads the OTA, then it extract and verify it. After Clicking on Install it will reboot directly. Does someone know how I do the OTA Updates on Android 12 correct?
Many thanks!
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
sunhao said:
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
Click to expand...
Click to collapse
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
This behavior is kind of weird from the OnePlus but I probably understand it. Anyway it will be better to offer full OTA straight forward. System can decide whether it's needed or not I think?
Anyway i reinstalled Magisk via fastboot when this happened.
Once twrp is available, there won't be those issues I assume.
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
sunhao said:
Android 12 it downloads the OTA, then it extract and verify it. When the Install Now button appears,switch to magisk and Install to inactive Slot in magisk.Don't restart phone in magisk,Switch to the system update interface and clicking on Install it will reboot directly.
Note the sequence of operations above,if you restart in magisk, the system will not be able to switch to the newly installed inactive Slot.
Click to expand...
Click to collapse
Thank you very much! I will try this for the next update
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
If oneplus offering the full update after this 3 times, will it reboot automatically after installation or is it there the same as in android 11 that I can reboot it over magisk?
paper88 said:
If oneplus offering the full update after this 3 times, will it reboot automatically after installation or is it there the same as in android 11 that I can reboot it over magisk?
Click to expand...
Click to collapse
Yes, you can. When the button to install now appears in the automatic update of the system, switch to magisk and install it to inactive Slot, then return to the system update, click the button to install now, and the phone will restart automatically. Remember not to click restart on the magisk interface
CoinsClassic said:
The issue for the author is that the incremental OTA is being downloaded and installed instead of the full-OTA, which makes it impossible to Patch Magisk into inactive slot.
The correct way is to NOT uninstall Magisk in the first place (Do not Recover Image in Magisk) -> Try to update the incremental OTA (it'll fail three times), then the updater will offer you the full-OTA (4.xxGB) which you can install and then switch to Magisk and install into inactive slot.
Click to expand...
Click to collapse
Do you know if this is also a possible way for the C.20 Update of Android 13? Would be helpful if someone tested this already