Hi Bill, thanks for replying. No i dont remember use MyApplication2 maybe from 10 to 11. I was updating by steps B1. This was done when I received the update notification, but I have not received it yet and I thought that I could iron the full version with B.2.1 Guide. Not even with the Bulgarian VPN I can get the update notification. What do you recommend me? Thank you
[GUIDE] Root and keeping root options
- Thread starter BillGoss
- Start date
Does your EU version of About device>Update have an option for doing a local install? If it does, try that.
If not, then either wait for the update notification or go hunting in the forums for other people updating to EU OOS 13.
So I decided to play around and see how things work on EU. And in the process of doing this I discovered that @Wishmasterflo's version of Orange Fox (OF) recovery https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/ will happily install an OOS zip that My Application 2 won't (fails verification). I used the OOS 13 v14 version of OF.
I successfully installed both NA OOS 13 and the EU OOS 13 downgrade. And also used the same OF to backup my EU OOS 12 installation!
So I suggest you try using OF to install your Oxygen Updater update zip.
I wanted to see if keeping root on the EU OOS 13 is the same as in NA.
I've documented what I did in the attached text note.
The main things I found out are:
I've documented what I did in the attached text note.
The main things I found out are:
- You can use the local install (About device>Update>3-dot menu>Local install) to install the downloaded (I used Oxygen Updater) OTA zip.
- You can use Magisk to install to inactive slot when the extraction finishes and BEFORE tapping on Install.
You should, however, pull a copy of the inactive boot image before using Magisk because it won't create a backup of the stock boot when you install to inactive. - You could also use Orange Fox to install the OTA and then use the the A.2 process (First time root) using Orange Fox
- The differences between NA and EU is all in the logical partitions, with the exception of the mdm_oem_stanvbk partition. See the
diffoutput in the attached note.
This means that you can use the same Magisk patched boot image for both the NA and EU OOS 13. I didn't check IN but someone with it could verify if the IN boot image md5sum is the same as the NA/EU one. - Orange Fox will install an OTA zip even if the local installer fails verification.
- You don't need to turn on airplane (AP) mode on EU before using a backup of /data - it was necessary on OOS 12 in TWRP. Orange Fox happily restored a backup taken without AP mode on.
Hi Bill, thanks for your work. Unfortunately, my EU kb2003 version does not have the local installation option. So I just have to wait for the notification or install OF and flash the OT
After Factory reset you can just unlock your bootloader again and install Magisk again to root it.
Factory reset will re-lock my bootloader? If yes, then I don't need root. Just need Google pay working fine for her.
No if you just do format data or factory reset from recovery it will not relock bootloader.
FYI, I've updated the OP for OOS 13 and now also include both TWRP and Orange Fox as custom recovery.
Hello,
l'm a but lost in all those posts because my case is special
I never updated to android 12 !
Can someone point me a step-by-step tutorial or a precise summary on how to update my 8T from android 11.0.13.13 KB05AA - KB2003 (Europe) rooted with magisk 23 (no twrp), to Android 13 KB2003 with magisk up to date, and safety-net passed? what version, which modules?
i actually use Universal safetynet Fix V2.1.3, systemless hosts, and Riru (for calls recording if i remember well, which seems to be a thing of the past sadly (?)
Im' currently downloading a rom called KB2003_11_F.13 on oxygen updater
(And i don't need to install any custom recovery, i always only used them to boot the phone (fastboot boot) to be able to root it next)
many thanks
PS: i don't have the current stock boot image
l'm a but lost in all those posts because my case is special
I never updated to android 12 !
Can someone point me a step-by-step tutorial or a precise summary on how to update my 8T from android 11.0.13.13 KB05AA - KB2003 (Europe) rooted with magisk 23 (no twrp), to Android 13 KB2003 with magisk up to date, and safety-net passed? what version, which modules?
i actually use Universal safetynet Fix V2.1.3, systemless hosts, and Riru (for calls recording if i remember well, which seems to be a thing of the past sadly (?)
Im' currently downloading a rom called KB2003_11_F.13 on oxygen updater
(And i don't need to install any custom recovery, i always only used them to boot the phone (fastboot boot) to be able to root it next)
many thanks
PS: i don't have the current stock boot image
Take a look at this great thread.
[GUIDE] Root and keeping root options
Update 230124: Add link to unofficial TWRP for OOS 13; some corrections and clarifications A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There are two ways to sourcing a copy of the stock...
forum.xda-developers.com
Unfortunately, you may need Magisk 25+ in order to use modified USNF in order to pass 2/3 play integrityHello,
l'm a but lost in all those posts because my case is special
I never updated to android 12 !
Can someone point me a step-by-step tutorial or a precise summary on how to update my 8T from android 11.0.13.13 KB05AA - KB2003 (Europe) rooted with magisk 23 (no twrp), to Android 13 KB2003 with magisk up to date, and safety-net passed? what version, which modules?
i actually use Universal safetynet Fix V2.1.3, systemless hosts, and Riru (for calls recording if i remember well, which seems to be a thing of the past sadly (?)
Im' currently downloading a rom called KB2003_11_F.13 on oxygen updater
(And i don't need to install any custom recovery, i always only used them to boot the phone (fastboot boot) to be able to root it next)
many thanks
PS: i don't have the current stock boot image
Safety Net is no longer relevant
I recently updated to A13 from A11 following these steps:
"You can use the local install (About device>Update>3-dot menu>Local install) to install the downloaded (I used Oxygen Updater) OTA zip.
You can use Magisk to install to inactive slot when the extraction finishes and BEFORE tapping on Install.
You should, however, pull a copy of the inactive boot image before using Magisk because it won't create a backup of the stock boot when you install to inactive." Credit to BillGoss.
Yes, I would update magisk to latest version before updating the android version. The only thing I haven't figured out is to get viper4android to work.
Thanks @Devtick.
I have the A13 Rom from Oxygen updater too, and already backed up the boot.img from it on the computer
Your sentence, do you mean "You can use Magisk to install to inactive slot when the (rom) INSTALLATION finishes and before tapping on REBOOT" ?
If so, then it's perfect i get it, last thing i have to figure out is how to update magisk from 23 to 25 first, without f** up everything
I'm not sure if i can safely "direct install" magisk 25.2 over an already rooted magisk23 rom (?)
Thanks a lot guys
I have the A13 Rom from Oxygen updater too, and already backed up the boot.img from it on the computer
Your sentence, do you mean "You can use Magisk to install to inactive slot when the (rom) INSTALLATION finishes and before tapping on REBOOT" ?
If so, then it's perfect i get it, last thing i have to figure out is how to update magisk from 23 to 25 first, without f** up everything
I'm not sure if i can safely "direct install" magisk 25.2 over an already rooted magisk23 rom (?)
Thanks a lot guys
Last edited:
Would you please share the link to that quote of mine because it is actually incorrect.
Please see section C. in the OP for the correct statement:
"When Magisk patches the boot image using either Magisk>Magisk Install>"Direct Install (Recommended)" or Magisk>Magisk Install>"Install to inactive slot" it creates a backup of the original stock boot image in a directory named /data/magisk_backup_<SHA1 of stock image>."
The writer missed some critical parts:
1. Use command to pull stock boot after OTA (or MSM read back). This will have a stock boot if reverting in Magisk doesn't work
2. Flash patched boot in fastbootd
BTW, I have yet decided to install A13 due to apps compatibility with rooted environment especially Netflix and cable TV apps
FYI, step 4 on B2.1 is wrong for Android 13 NA, I followed the steps installing to inactive slot before clicking "install now" from the MyApplication2 app in Android 12, it did end up prompting to reboot so the initial extraction does not install the boot partition, or whatever is done is overwritten during the install process.
Now my phone is f*cked as it won't boot to the old Android 12 slot..not blaming anyone but just FYI if anyone is attempting to go from rooted A12 to A13 Global using that method, make sure to install to inactive slot AFTER clicking Install Now and BEFORE rebooting...
Edit: thankfully since A13 is a full update and not incremental, if anyone runs into the same issue it's easy to patch the boot.img from the OTA using the payload dumper in the OP, boot from the patched boot, and then direct install to retain root for future OTAs.
Now my phone is f*cked as it won't boot to the old Android 12 slot..not blaming anyone but just FYI if anyone is attempting to go from rooted A12 to A13 Global using that method, make sure to install to inactive slot AFTER clicking Install Now and BEFORE rebooting...
Edit: thankfully since A13 is a full update and not incremental, if anyone runs into the same issue it's easy to patch the boot.img from the OTA using the payload dumper in the OP, boot from the patched boot, and then direct install to retain root for future OTAs.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Yes I rooted a13 with TWRP but it can also be rooted through patch boot img method -
35Update 230124: Add link to unofficial TWRP for OOS 13; some corrections and clarifications
A. First time rooting
This process is common across all options
A.1 Flashing Magisk patched boot image
There are two ways to sourcing a copy of the stock boot image (other than using TWRP - See A.2).
- Using the MSM Tool readback option to pull a copy of the current boot image from the phone
- Using Payload Dumper and a full update zip
A.1.1 Using MSM Tool ReadBack
The MSM Tool has a feature (ReadBack) that allows it to pull copies of partitions from a phone when it is connected in EDL mode to a PC.
This means that you can pull a copy of your currently running stock boot image directly from the (unrooted) phone and you are not dependent on having access to a full rom installation zip.
A big thanks to @scottlam1 for this information (see https://forum.xda-developers.com/t/oxygenos-a12-breaks-rooting.4456251/post-87067419 and following). You can get a copy of the MSM Tool from @Some_Random_Username's https://forum.xda-developers.com/t/...ol-to-restore-your-device-to-oxygenos.4180837. I used the one for OOS 11.0.7.9 for KB05AA when testing this process.
- Find your current slot by connecting your phone to your PC and running
adb shell getprop ro.boot.slot_suffixNote: on OOS 12 when you connect the phone to the PC you must enable "Transfer files" on the phone for ADB to see the device. - Start MsmDownloadTool V4.0.exe
- Select User type: Others and click Next
- Press F8
- Select the appropriate boot partition (boot_a or boot_b based on the getprop result). Note: do NOT select both boot_a and boot_b because ReadBack will only produce one boot.img file and the _b extract will overwrite the _a extracted file.
- Enter the password: oneplus and then press OK. You should now see a ReadBack button underneath the Target dropdown list.
- Reboot the phone into EDL mode using
adb reboot edl. When you see it connected to the MSM Tool - it will show an entry with COM3 (for example) - click on the ReadBack button.
Warning: Do NOT click on the Start button as this will start the installation process and reset your phone. - MSM will show "ReadBack Complete" (in green) when it has copied the boot image and power off the phone. Close the MSM tool.
- Disconnect the phone from the PC, turn on your phone, reconnect it to the PC, and copy the boot image (it's in C:\boot.img) to your phone.
- The rest of the process is the same as that in section A.1.2 below, but starting from step 6 in @DroidFreak32's guide as you already have the boot image.
A.1.2 Using Payload Dumper
Notes:
- This can ONLY be used on full update zips, NOT on incremental updates.
- Note: if you use @mslezak's Payload Dumper (see https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/ then you may be able to use it on incremental updates. I personally have not done this.
- You can use the latest stable version of Magisk (my recommendation as of June 2022)
- Do NOT use the "To flash" option in step 11 because this causes issues when you get the next OTA update. Use the the "To Temporarily boot into a rooted system (RECOMMENDED!!)" option.
- Backup both the stock boot and Magisk patched boot images if you are going to use CLI
A.2 Using TWRP or Orange Fox
I will use TWRP throughout the document to mean TWRP or Orange Fox unless indicated otherwise.
I use the TWRP installer zip to create an installer for Orange Fox by replacing the recovery.img file in the TWRP installer zip with the Orange Fox recovery image (the file has to be named recovery.img). The advantage of this is that you can then flash the recovery zip in recovery as well as in Magisk (install it as a module). And the installer zip will flash recovery to both slots.
Notes:
- on OOS 11 use TWRP 11 from https://dl.twrp.me/kebab/
- on OOS 12 use the WIP TWRP 12 version from https://forum.xda-developers.com/t/...roject-8t-9r-2022-07-27.4473983/post-87271673 or Orange Fox from https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/
- on OOS 13 use Orange Fox for OOS 13 from https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-22-nov-2022.4391139/ or @apophis9283's version of TWRP from https://forum.xda-developers.com/t/recovery-unofficial-twrp-oneplus-8t-oos13-1-19-23.4541965/
- Boot bootloader
fastboot boot <twrp.img>- (optional - see next item) Backup current boot
- Install Magisk-*.apk and note that Magisk will create a backup of the current stock boot (see section C)
- Install@kdrag0n's Universal SafetyNet Fix Magisk module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://github.com/kdrag0n/safetynet-fix/releases)
- Reboot system
- Uninstall Magisk stub
- Install Magisk-*.apk and in Magisk>Settings enable both Zygisk and Enforce DenyList
- Reboot system
A.2.1 Keep TWRP
If you want to keep TWRP installed then the process is very similar to that described for Magisk. The difference is that this time we backup recovery and install TWRP. You can merge the Magisk process with the TWRP process by: Backing up current boot and recovery; Installing both the Magisk-*.apk and the TWRP installer zip.
Here's the process for just TWRP:
- Boot bootloader
fastboot boot <twrp.img>- Backup current recovery
Note: the TWRP backups of physical partitions (like boot and recovery and so on) are actually image dumps. You could rename the files from *.emmc.win to *.img and install them using TWRP or other methods. - Install TWRP installer zip
- Reboot system
B. Keeping root during an update
B.1 System Update downloads and installs the update
This is using the built-in System Update tool, which you'll find in:
- OOS 11: Settings>System settings> System Update
- OOS 12 and higher: Settings>About device>Software update
- Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
- Download and Install the update (and DO NOT reboot) using:
OOS 11: Settings>System Settings>System Update>Download and Install
OOS 12 and higher: Settings>About device>Software update - Copy the updated boot image as follows:
- On PC:Find the inactive slot suffix:
adb shell getprop ro.boot.slot_suffixNote: on OOS 12 when you connect the phone to the PC you must enable "Transfer files" on the phone for ADB to see the device.- If the result is _a then the inactive slot suffix is _b otherwise it is _a
- Take a copy of the inactive slot boot image:
adb shell su -c dd if=/dev/block/by-name/boot<inactive slot suffix> of=/sdcard/oos-ota-boot.imgreplacing <inactive slot suffix> with the value you previously determined (_a or _b). Note: Magisk may prompt you (on your phone) to grant root access to Shell - grant it.
- On PC:Find the inactive slot suffix:
- On phone: Patch the dumped oos-ota-boot.img using Magisk>Magisk Install>"Select and Patch a File"
- Copy /sdcard/Download/magisk_patched*.img to your PC
- Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
- Turn on Airplane Mode to prevent Google Play Services detecting that the phone is bootloader unlocked and making your phone uncertified in Google Play.
- Reboot the phone from the System Update dialog; verify that you are now running the updated version
- On PC: Reboot to bootloader using
adb reboot bootloader - Boot (NOT flash) the patched boot image:
fastboot boot <magisk-patched image>where <magisk-patched image> is the patched image you transferred to the PC - On phone: Verify that Magisk shows you are rooted
- Make rooting permanent using Magisk>Magisk Install>"Direct Install (Recommended)" and reboot again
- Turn off Airplane Mode
B.2 Manual Install
This involves manually downloading the update zip and then installing it using one of the following options.
It is up to you to download the update (from whichever source you use).
How I get a copy of the update zip
Note: I'm running the NA version of OOS. If the URL below for the OTA is different for other OOS versions, please let me know via a PM.
Once the phone tells me that there's an update available I do the following in Termux (https://f-droid.org/en/packages/com.termux/):
su -c "logcat -d" | grep -Eo "https://android.googleapis.com/packages/ota-api/package/[a-z0-9]*.zip"
This looks for the the Google OTA server file name in logcat and returns the source address. For example, the KB2005 C.11 full update was https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Note 1: You should run these commands as soon as you get a notification that you have the update. If you leave it too long then the log file will roll over and you won't be able find the url.
Note 2: You could also useadb shellto run thelogcat -d | grep ...commands, though I've never done that because I prefer to do everything on my phone, where possible.wget -O /sdcard/oos-ota-update.zip <source address>
This pulls a copy of the file to /sdcard.
Note: You could also just paste the URL into a browser to download the file.
B.2.1 Local Install
This is using:
- OOS 11: System Update>Gear icon (local install)
- OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
- OOS 13: On EU and IN Settings>About device>Software update>3-dot menu>Local install; to be advised on NA
- If you have TWRP installed then reboot recovery, restore the stock OOS recovery (you would/should have taken a copy of it when you installed TWRP as mentioned in A.2.1), and reboot system. Without doing this, an incremental OTA will fail when it checks for the stock recovery.
- Move the update zip to /sdcard (NOT a subdirectory of /sdcard)
- Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk
- Install the update using the appropriate local installer for your version of OOS and DO NOT reboot
Note that the OOS 13 EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it and it is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting, leaving you without root. - Restore root to the current slot using Magisk>Magisk Install>"Direct Install (Recommended)". This is so you keep root in case the update somehow fails and you're returned to the current system.
- Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
- On OOS 13 now tap on Install in the local updater process; on OOS 11 and 12 reboot
- To re-install TWRP, follow the process in A.2.1
B.2.2 Using TWRP (placeholder)
There may be a way of using TWRP but I've never tried it.
B.2.3 Using CLI
CLI (command line interface) tools, such as Terminal (I use Termux from https://f-droid.org/en/packages/com.termux/) or ADB shell, allows you to manually download delta updates avoiding the need to wait for full updates or for someone to post a copy of the delta update zip.
If you use Terminal then you can install updates without the need of a PC (my preferred option).
Using line commands, at one level, can simplify some processes by avoiding the need to switch out to recovery and back again. On the other hand, they complicate things by requiring knowledge of how to use them.
The commands you need to be familiar with are:
ddto read-from/write-to the partitions in /dev/block/by-namegrepto scan the output of a logcatgetpropto find out which are the active/inactive slotslogcatto read the Android logssuto run commands as root
- Get a copy of the update zip
Note: I'm running the NA version of OOS. If the URL below for the OTA is different for other OOS versions, please let me know via a PM.
Once the phone tells me that there's an update available I do the following in Termux:su -c "logcat -d" | grep -Eo "https://android.googleapis.com/packages/ota-api/package/[a-z0-9]*.zip"
This looks for the the Google OTA server file name in logcat and returns the source address. For example, the KB2005 C.11 incremental update was https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Note: You should run these commands as soon as you get a notification that you have the update. If you leave it too long then the log file will roll over and you won't be able find the url.wget -O /sdcard/oos-ota-update.zip <source address>
This pulls a copy of the file to /sdcard
Note: You could also just paste the URL into a browser to download the file
- Find the active slot suffix:
getprop ro.boot.slot_suffix
If the result is _a then the inactive slot suffix is _b otherwise it is _a - Restore active slot stock boot/recovery (recovery: only if TWRP is installed) using
dd if=<copy of stock boot/recovery> of=/dev/block/by-name/<boot/recovery><active slot suffix>
Note: you could also use Magisk to restore the stock boot using Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk - Install the update using the appropriate local installer for your version of OOS and DO NOT reboot
Note that the OOS 13 EU/IN local installer will first extract the update (and update the inactive slot partitions) and then prompt you to Install it. It is IMPERATIVE that you DON'T CLICK on Install at this point as it will finish the installation and reboot without prompting leaving you without root.
The local installer is:- OOS 11: System Update>Gear icon (local install)
- OOS 12: MyApplication2 app (source: https://oxygenos.oneplus.net/English_20220225101104.apk; see https://forums.oneplus.com/threads/oxygenos-12-for-the-oneplus-8t.1555060/)
- OOS 13: On EU and IN Settings>About device>Software update>3-dot menu>Local install; to be advised on NA
- Backup the new inactive slot stock boot/recovery (recovery: only if TWRP is installed) using
dd if=/dev/block/by-name/<boot/recovery><inactive slot suffix> of=<new boot/recovery img> - Restore root to the current active slot
dd if=<copy of current Magisk patched stock boot/recovery> of=/dev/block/by-name/<boot/recovery><active slot suffix>. This is so you keep root in case the update somehow fails and you're returned to the current system.
Note: You could also use Magisk>Magisk Install>"Direct Install (Recommended)" - (ONLY if keeping TWRP) Magisk>Modules>Install from storage: Select <twrp-installer.zip>
- Magisk>Magisk Install>"Install to inactive slot" and DO NOT reboot
- Backup the new Magisk patched stock boot using
dd if=/dev/block/by-name/<boot><inactive slot suffix> of=<new Magisk patched boot img> - On OOS 11 and 12: Reboot. On OOS 13 now tap on Install in the local installer to finish the installation.
C. A note on Magisk backup folders in /data
When Magisk patches a stock boot image using either Magisk>Magisk Install>"Direct Install (Recommended)", Magisk>Magisk Install>"Install to inactive slot", or is installed in TWRP, then it creates a backup of the stock boot image in a directory named /data/magisk_backup_<SHA1 of stock image>.
When you use Magisk>Uninstall Magisk>Restore images the backup corresponding to the current patched boot image is used to restore the stock image to the current (active) slot.
Clearly, if you deleted these magisk_backup directories then Magisk will not be able to restore the stock boot image. You must, therefore, always keep the current backup.
If you don't delete these backups you can end up with a lot of obsolete backups. So, how to work out which one is the one you need to keep?
The simplest way is to:
- Restore the current stock boot image using Magisk>Uninstall Magisk>Restore images
- Delete all the /data/magisk_backup_* directories
- Restore the rooted boot image using Magisk>Magisk Install>"Direct Install (Recommended)" - this also creates a new magisk_backup directory (no need to reboot)
3I'm very pleased to announce that I've updated the OP with a significant new process (see section A.1.1) for first time rooting.
You now no longer need to rely on a full update zip being available as you can use the MSM Tool to pull the stock boot image directly from your phone.
I'm indebted to @scottlam1 for sharing this feature of the MSM Tool.
(And, yes, I've tested this)3Okay I was courious and tried to root my KB2005 (GLO) with incremental Update .C16 (since there is no Full OTA yet).
I used @BillGoss guide from OP (Update 20220427 WIP) in combination with @osm0sis method (also mentioned in OP and it worked! -> Kudos to both of them.
These were my steps:
- UNROOT current slot in magisk app (=uninstall +restore images) WITHOUT REBOOTING
- Download and Install the C16 incremental update from built-in Software Update function WITHOUT REBOOTING
- Dump the fresh updated boot_img from the inactive slot (find your active slot with ->
using the command BillGoss mentioned ->Code:
adb shell getprop ro.boot.slot_suffix(in my case the inactive slot=b please change accordingly refering to your currently inactive slot -> boot_a or boot_b)Code:adb shell su -c dd if=/dev/block/by-name/boot_b of=/sdcard/update-boot.img - patch the dumped update-boot.img with magisk -> "Select and Patch a File"
- copy the magisk_patched.img to your PC
- Re-root the current slot using the Magisk app direct Install, so in case the update somehow fails you'll be back where you started (rooted on the current slot) (THX to osm0sis for this step)
- turn on Airplane Mode
- reboot phone from update dialog, let it boot up and check if you are now on the updated slot
- reboot to fastboot e.g. using this command ->
Code:
adb reboot bootloader - fastboot boot the magisk_patched.img ->
Code:
fastboot boot .\magisk_patched.img - boot up and check in magisk app if you are now rooted
- in magisk app do a "Direct Install" and reboot again
- now you are on the updated slot with persistent magisk root
- turn off Airplane Mode and enjoy.
3
Install this and you will have local upgrade
