• We are moving to xdaforums.com!

    Posts made between now and when the migration is complete will not be carried over.
    You will be automatically redirected once the migration is complete.

[GUIDE] Root and keeping root options

Search This thread
By:
Advanced…
SourPower

SourPower

Senior Member
Nov 21, 2014
555
118
East
BillGoss said:
When you start the MSM tool as described in the OP, your screen should look like the screenshot MSM-b4-conn.png
After you run adb reboot edl your phone should reboot to EDL mode (it'a a black screen) and you should see it show up in Device Manager after about 10 s.
The MSM tool should then look like screenshot MSM-af-conn.png
And in Device Manager it should show up like in screenshot DevMan.png
Note that if you don't do anything the phone will reboot normally after 25 s.

If you don't get the phone showing up in Device Manager as expected, then you should fix this problem - and I can't help you with that. You'll need to take this to another thread - either the MSM tool thread or start one in the Q&A forum.
Resolving MSM tool connection problems is off-topic in this thread.
Click to expand...
Click to collapse
thank you, i was able to quickly get the read back
 
  • Like
Reactions: BillGoss
F

Feduz

Senior Member
Jun 1, 2014
130
18
OnePlus 8T
I've updated as always to KB2003_11_F.63. But I cannot be able to modify/update the hosts file (via LP to block ads). I've flashed also via Magisk "systemless hosts - unified" by gloeyisk but with no success. Any tips to verify which is the problem?
 
BillGoss

BillGoss

Senior Member
Sep 2, 2010
5,682
5,010
Sydney
Feduz said:
I've updated as always to KB2003_11_F.63. But I cannot be able to modify/update the hosts file (via LP to block ads). I've flashed also via Magisk "systemless hosts - unified" by gloeyisk but with no success. Any tips to verify which is the problem?
Click to expand...
Click to collapse
Ask your question in the Magisk forum.
How to use Magisk modules is off topic in this thread..
 
T

TheZorg

Senior Member
Nov 25, 2012
83
22
OnePlus 3T
OnePlus 8T
BillGoss said:
Interesting post in OnePlus Community: https://community.oneplus.com/wap/thread/1274315994487586816

I had the boot loop issue when I rebooted from the Magisk reboot screen. I got the phone into bootloader, switched slots, rebooted, and it came up on F.15. I went to the Updater screen and it showed me that it was ready to install. I tapped on the Install button and it rebooted and came up on F.62.

On my other 8T, I rebooted from the Updater screen (NOT the Magisk screen) after installing Magisk to the inactive slot and that worked perfectly.

I have no idea what holding down the Vol Up key does to make a difference to the boot looping.
Click to expand...
Click to collapse
This post was a godsend, the same thing happened to me when updating from F.62 to F.63, but I followed your steps and everything is fine now. I think it might be a good idea to add a link to this post in the B.2.1 section for emergency reasons, with a message along the lines of "If you rebooted from the Magisk screen, follow these steps".
 
BillGoss

BillGoss

Senior Member
Sep 2, 2010
5,682
5,010
Sydney
TheZorg said:
This post was a godsend, the same thing happened to me when updating from F.62 to F.63, but I followed your steps and everything is fine now. I think it might be a good idea to add a link to this post in the B.2.1 section for emergency reasons, with a message along the lines of "If you rebooted from the Magisk screen, follow these steps".
Click to expand...
Click to collapse
Thanks, I'll think about your suggestion.
 
  • Like
Reactions: TheZorg
BillGoss

BillGoss

Senior Member
Sep 2, 2010
5,682
5,010
Sydney

Attachments

  • Screenshot_20230403-20224458.jpg
    Screenshot_20230403-20224458.jpg
    81.1 KB · Views: 16
  • Like
Reactions: Fredator and Feduz
BillGoss

BillGoss

Senior Member
Sep 2, 2010
5,682
5,010
Sydney
TheZorg said:
This post was a godsend, the same thing happened to me when updating from F.62 to F.63, but I followed your steps and everything is fine now. I think it might be a good idea to add a link to this post in the B.2.1 section for emergency reasons, with a message along the lines of "If you rebooted from the Magisk screen, follow these steps".
Click to expand...
Click to collapse
Are you on KB2005 (NA) and use the apk to do the local install? Because on EU/IN the reboot happens automatically when you tap on Install.
 
BillGoss

BillGoss

Senior Member
Sep 2, 2010
5,682
5,010
Sydney
TheZorg said:
I'm on KB2003, I used the built-in local installer but had a brain fart and forgot to tap Install instead of rebooting from Magisk after rooting the inactive slot.
Click to expand...
Click to collapse
Ah, so you didn't actually finish the install process (step 7 in B.2.1) and revoked from Magisk. And that's why you got a boot loop and had to follow the other quoted post of mine. Right?
 
T

TheZorg

Senior Member
Nov 25, 2012
83
22
OnePlus 3T
OnePlus 8T
BillGoss said:
Ah, so you didn't actually finish the install process (step 7 in B.2.1) and revoked from Magisk. And that's why you got a boot loop and had to follow the other quoted post of mine. Right?
Click to expand...
Click to collapse
Yes, exactly. The whole process was: extracting the full zip with the local updater; once it finished I reinstalled Magisk via direct install first, then installed to the inactive slot, after which I pressed the reboot button on the Magisk screen instead of switching back to the local installer and pressing install.
 
  • Like
Reactions: BillGoss
BillGoss

BillGoss

Senior Member
Sep 2, 2010
5,682
5,010
Sydney
TheZorg said:
Yes, exactly. The whole process was: extracting the full zip with the local updater; once it finished I reinstalled Magisk via direct install first, then installed to the inactive slot, after which I pressed the reboot button on the Magisk screen instead of switching back to the local installer and pressing install.
Click to expand...
Click to collapse
I've updated the OP and added a note to B.2.1 step 6.
 
  • Like
Reactions: TheZorg
AlexCmb

AlexCmb

Senior Member
May 31, 2016
199
47
OnePlus 8T
Hello,
I'm trying to update my OP8T but the local install update option is not clickable.
Someone know why ? I assume my phone is rooted and that's why I want to use this option.
My OOs version is KB2003_11_F.15.
Is it possible to use the "MyApplication2" app?
Thanks a lot.

IMG_20230407_180245.jpg
 
You must log in or register to reply here.

Similar threads

DroidFreak32
[Guide] How to ROOT OnePlus8T (CN/IN/EU/International) KB2000,KB2001,KB2003,KB2005
Replies
705
Views
155K
E
ecompton59
C
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
Replies
2K
Views
163K
L
lqtdc
Mpolo87
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
Replies
213
Views
49K
dangerousnerdrays
dangerousnerdrays
Mbektic
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
Replies
92
Views
109K
Bofahad
Bofahad
B
[GUIDE] Fix/Enable 5G and DSS
Replies
184
Views
59K
Rootk1t
Rootk1t

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    angus6969
    angus6969
    Hi guy, following an update to a13.1 (KB2003_13.1.0.581(EX01)) due to a distraction, I pressed install and instead the phone restarted, I lost the root, I tried several times with magisk patching the boot. Img but I can't restore the root. Is there a way to regain root without losing the current installation?
    View
    1
    BillGoss
    BillGoss
    angus6969 said:
    I also tried the previous versions. I can't get root anymore. Can I downgrade to the previous version without formatting?
    Click to expand...
    Click to collapse
    I managed to do that only once. But every other time I've tried it, I've had to format data to get the phone working again.
    You could, however use TWRP or Orange Fox to backup /data and copy your user data (/sdcard) to your PC. Then you can restore your app and user data after you've upgraded again.

    The trick to downgrading is install the full zip (in this case of .580) using TWRP or OF. Then reboot to recovery (this is the crucial step) which will be the stock recovery you've just installed, and format data. Only then can you reboot the phone properly.
    After you've rooted and upgraded (in whichever order you choose) you can restore the data backups you took.
    View
    1
    J
    JimDandy68
    JimDandy68 said:
    Thanks, @BillGoss!
    Click to expand...
    Click to collapse
    I just used dd to restore stock, then followed some of the other instructions in B.2.2. I used the incremental update. All seems fine, and root remains. Thanks again.
    View
  • 40
    BillGoss
    BillGoss
    Update 230920: Recommend Magisk Stable for first time rooting

    A. First time rooting​

    OP8T Root options-First time rooting.png

    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).
    1. Using the MSM Tool readback option to pull a copy of the current boot image from the phone
    2. 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.
    1. Find your current slot by connecting your phone to your PC and running adb shell getprop ro.boot.slot_suffix Note: 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.
    2. Start MsmDownloadTool V4.0.exe
    3. Select User type: Others and click Next
    4. Press F8
    5. 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.
    6. Enter the password: oneplus and then press OK. You should now see a ReadBack button underneath the Target dropdown list.
    7. 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.
    8. MSM will show "ReadBack Complete" (in green) when it has copied the boot image and power off the phone. Close the MSM tool.
    9. 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.
    10. 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:
    Follow the instructions detailed in @DroidFreak32's https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/ paying attention to:
    1. Use the latest stable version of Magisk (my recommendation as of June 2022)
    2. 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.
    3. Backup both the stock boot and Magisk patched boot images if you are going to use CLI
    I also recommend that on OOS you install @Displax's Universal SafetyNet Fix Magisk MOD module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://forum.xda-developers.com/t/module-mod-universal-safetynet-fix.4553699/).

    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:
    1. Boot bootloader
    2. fastboot boot <twrp.img>
    3. (optional - see next item) Backup current boot
    4. Install Magisk-*.apk and note that Magisk will create a backup of the current stock boot (see section C)
    5. Install @Displax's Universal SafetyNet Fix Magisk MOD module v2.4.0 or later to pass Play Integrity with an unlocked bootloader (https://forum.xda-developers.com/t/module-mod-universal-safetynet-fix.4553699/)
    6. Reboot system
    7. Uninstall Magisk stub
    8. Install Magisk-*.apk and in Magisk>Settings enable both Zygisk and Enforce DenyList
    9. 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:
    1. Boot bootloader
    2. fastboot boot <twrp.img>
    3. 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.
    4. Install TWRP installer zip
    5. Reboot system

    B. Keeping root during an update​

    OP8T Root options-Keeping root.png

    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
    The process is complicated because you cannot use Magisk>Magisk Install>"Install to inactive slot" as this will fail on OOS 11 (for incremental updates) and OOS 12 (for all updates, including the initial update from OOS 11 to OOS 12).
    But testing on OOS 13 (updating from F.62 to F.63 on KB2003 and KB2005) shows that you can now use "Install to inactive slot" and, therefore, the simpler B.1.2 process can be used with System Updater for both incremental and full OTA updates. However this needs more testing (by adventurous IN users).

    B.1.1 Safe​

    The following process is safe to use on all versions and types of OTA updates. It is courtesy of @osm0sis in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713 and @rage302 in https://forum.xda-developers.com/t/...ing-root-options.4387977/page-4#post-86830285.
    1. 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.
    2. Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
    3. 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
    4. Copy the updated boot image as follows:
      • On PC:Find the inactive slot suffix:
        • adb shell getprop ro.boot.slot_suffix Note: 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.img replacing <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.
    5. On phone: Patch the dumped oos-ota-boot.img using Magisk>Magisk Install>"Select and Patch a File"
    6. Copy /sdcard/Download/magisk_patched*.img to your PC
    7. 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.
    8. Turn on Airplane Mode to prevent Google Play Services detecting that the phone is bootloader unlocked and making your phone uncertified in Google Play.
    9. Reboot the phone from the System Update dialog; verify that you are now running the updated version
    10. On PC: Reboot to bootloader using adb reboot bootloader
    11. 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
    12. On phone: Verify that Magisk shows you are rooted
    13. Make rooting permanent using Magisk>Magisk Install>"Direct Install (Recommended)" and reboot again
    14. Turn off Airplane Mode

    B.1.2 Simple​

    The following process is the simplest update method, but is limited to:
    • OOS 11 full image OTAs only
    • OOS 13+ full image OTAs and, starting with C.62, incremental OTAs (confirmed for KB2003 and KB2005)
    1. 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.
    2. Restore the current stock boot image using Magisk>Uninstall Magisk>"Restore images" and DO NOT reboot
    3. Download and Install the update (and DO NOT reboot) using:
      OOS 11: Settings>System Settings>System Update>Download and Install
      OOS 13+: Settings>About device>Software update
      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.
    4. 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.
    5. Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
      Note: if you accidentally reboot from Magisk at this point and end up in a bootloop (EU and IN), see: https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/page-17#post-88204853
    6. On OOS 13+ EU and IN now tap on Install in the local updater process and on NA tap Reboot; on OOS 11 reboot.
    7. To re-install TWRP, follow the process in A.2.1

    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 to get a copy of the update zip
    The simplest option is to use Oxygen Updater (https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater).
    It is also possible to get a copy of the update zip if the OOS 13+ System Updater is showing that an update is available and the installation button is showing "Extract".
    You'll find the installation zip (named my_manifest_*_patch.zip or my_manifest_*_all.zip for incremental or full OTA) in /data/ota_package/OTA/.otaPackage.

    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; on NA: same as for OOS 12
      Note: If the Local install option is greyed out because the System Updater is showing that an update is available, then you can still use Local install by:
      1. Turn on Airplane mode to prevent the System Updater finding the update again after the next step.
      2. Go to Settings>Apps>App Management>3-dot menu>Show system and clear storage from Software update
        Software updater.png
    1. 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.
    2. Move the update zip to /sdcard (NOT a subdirectory of /sdcard).
    3. Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk.
    4. 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.
    5. 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.
    6. Root the updated boot image using Magisk>Magisk Install>"Install to inactive slot"
      Note: if you accidentally reboot from Magisk at this point and end up in a bootloop (EU and IN), see: https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/page-17#post-88204853
    7. On OOS 13+ EU and IN now tap on Install in the local updater process and on NA tap Reboot; on OOS 11 and 12 reboot.
    8. To re-install TWRP, follow the process in A.2.1

    B.2.2 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:
    • dd to read-from/write-to the partitions in /dev/block/by-name
    • grep to scan the output of a logcat
    • getprop to find out which are the active/inactive slots
    • logcat to read the Android logs
    • su to run commands as root
    1. 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:
      1. 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.
      2. 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
    2. 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
    3. 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
    4. 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:
    5. 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>
    6. 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)"
    7. (ONLY if keeping TWRP) Magisk>Modules>Install from storage: Select <twrp-installer.zip>
    8. Magisk>Magisk Install>"Install to inactive slot" and DO NOT reboot
    9. Backup the new Magisk patched stock boot using dd if=/dev/block/by-name/<boot><inactive slot suffix> of=<new Magisk patched boot img>
    10. 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:
    1. Restore the current stock boot image using Magisk>Uninstall Magisk>Restore images
    2. Delete all the /data/magisk_backup_* directories
    3. Restore the rooted boot image using Magisk>Magisk Install>"Direct Install (Recommended)" - this also creates a new magisk_backup directory (no need to reboot)
    View
    4
    BillGoss
    BillGoss
    After my rather messy update to F.15 (see https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/post-87960237) I'm very pleased to say that the update to F.62 was a breeze.
    Here's what I did:
    I didn't wait for the update to get to my phone. Instead I downloaded the incremental update for KB2003 using Oxygen Updater.
    Then I followed process B.2.3 CLI because it's my preferred method since no PC is required. Note, however, that I make really sure that my phone (including TWRP backups) are synced to my PC before I start in case anything goes seriously wrong.
    And, I'm happy to say, it worked like a charm! Simple!
    View
    4
    BillGoss
    BillGoss
    FYI, I've updated the OP for OOS 13 and now also include both TWRP and Orange Fox as custom recovery.
    View
    3
    rage302
    rage302
    Okay 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:

    1. UNROOT current slot in magisk app (=uninstall +restore images) WITHOUT REBOOTING
    2. Download and Install the C16 incremental update from built-in Software Update function WITHOUT REBOOTING
    3. Dump the fresh updated boot_img from the inactive slot (find your active slot with ->
      Code: 
      adb shell getprop ro.boot.slot_suffix
      using the command BillGoss mentioned ->
      Code: 
      adb shell su -c dd if=/dev/block/by-name/boot_b of=/sdcard/update-boot.img
      (in my case the inactive slot=b please change accordingly refering to your currently inactive slot -> boot_a or boot_b)
    4. patch the dumped update-boot.img with magisk -> "Select and Patch a File"
    5. copy the magisk_patched.img to your PC
    6. 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)
    7. turn on Airplane Mode
    8. reboot phone from update dialog, let it boot up and check if you are now on the updated slot
    9. reboot to fastboot e.g. using this command ->
      Code: 
      adb reboot bootloader
    10. fastboot boot the magisk_patched.img ->
      Code: 
      fastboot boot .\magisk_patched.img
    11. boot up and check in magisk app if you are now rooted
    12. in magisk app do a "Direct Install" and reboot again
    13. now you are on the updated slot with persistent magisk root
    14. turn off Airplane Mode and enjoy.
    greetings rage
    View
    3
    A
    agpol07
    g4seb said:
    @BillGoss Hello, I was in oos11 Root without twrp. In oos11 to make the upgrade, I made installation in local mode, then in magisk I reinstalled the one "after OTA" then reboot. To upgrade to OOS12 I did the same thing. But now, how to make an upgrade C15 -> C16 for example, without brick the phone since there is no more the option to install in local mode (Gear icon) ???
    Click to expand...
    Click to collapse
    Install this and you will have local upgrade

    View

New posts