Database Users

Root and update firmware from 6.0.1

I rooted the phone (XT1642) using this guide: https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
I'm on 6.0.1 and have been getting the install system update prompt (NPJ25.93-14) every time I turn WiFi on.
Can I just install this or will it remove the rooting I did?
If it removes the root, how do I update to the latest firmware safely and root it?
Alternatively, how do I get rid of the prompt each time I turn WiFi on?
Can I take an image of my phone as it is and revert back to it at any time, and if so, how?
I really don't know what I'm doing and help would be appreciated.

If you're looking to update to NPJ25.93-14 via OTA, you'll need to unroot and flash a stock recovery (and stock logo.bin if you hid your bootloader warning), else the OTA will not install. Of course, this will remove root and TWRP until you've updated. Also, bear in mind after the update there's 2 more security patches (March and June 2017)
Before attempting anything though, ensure you've got a backup of your data (including a TWRP backup of your device as it is) and move them off your device until you're completed.
If you don't have access to a stock recovery/logo.bin, you could use a stock fastboot ROM to bring you up to date - this will remove root and TWRP however. The latest fastboot ROM we have is the March 2017 build: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
If you wish to update with the fastboot ROM (so bringing you up to the March 2017 build), you may wish to use the following fastboot commands, which will replace your recovery and remove root, but should not affect your data (however as with anything that affects your system, ensure you have backups regardless)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
This fastboot ROM will formally update your device completely to NPJS25.93-14-4 (March 2017), but using these commands you will not have locked your bootloader. You may wish to wait for the June security patch (since OTA updates require a stock recovery, stock kernel and stock system) or proceed to rooting.
If you wish to root on Nougat, follow either: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 or https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270 Please ensure that you flash a custom kernel before rooting on stock - Motorola - Nougat on Moto G4/Plus devices.
If you do not wish to fastboot a stock ROM, you could flash a TWRP flashable of the March build. This will not update your bootloader, or GPT partitions (so will not completely update your device to the March build), but is a nice shortcut. Again, this will remove root (but not TWRP) and so you will have to re-root as for Nougat. https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 for the TWRP flashable. This will also require you to flash the modem TWRP flashable file (included in the thread) as your fingerprint sensor may not work properly otherwise.
If you don't wish to update, and just want to disable the notification, have a look here: https://forum.xda-developers.com/mo...ble-notification-update-t3459587/post73005893

Thank you very much for the detailed answer. I have tried my best to understand the scene as best I can, but remain unfamiliar with the various approaches.
I have made a backup of my SD Card and used TWRP to create a backup of partitions: System (1983MB), Data (3459MB) and Boot (16MB) and transferred them to my PC
I am able to restore to my old 6.01 configuration with this backup I made provided I have an unlocked bootloader right?
To follow the guide you linked for rooting Android 7.0: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Am I correct in saying I would need to unroot my 6.0.1, re-lock the bootloader and then update to the latest firmware via OTA updates? You say to "flash a custom kernel before rooting" but I don't know what this means or how I would do it.
Alternatively, I see the June security patch came out today. Would this be an easier or better way to update than the above method?

I don't know if you'll be able to revert back to your old 6.0.1 TWRP backup once you've updated to Nougat, as the modem and other firmware would be newer than 6.0.1. Additionally, if you've updated to the June update, be very careful about downgrading by flashing a stock ROM as the bootloader has been updated in this update, and attempts to downgrade the bootloader and GPT seem to result in bricking of devices (though TWRP flashes do not care about the bootloader and GPT usually, so you may be okay in that regard).
As for the procedure for updating, you do not have to re-lock your bootloader if you desire root later. Bootloader lock status does not appear to affect OTA updates/installations - only the presence of a non-stock recovery, system or kernel will cause the update to abort. Re-locking for your purpose, unless you're wanting to send your device for service or to sell it, is unnecessary so leave it unlocked. The unlocking instructions in the guide are only there if you're coming from a device with a locked bootloader. If you're going down the OTA route, a general guide would be:
1)Unroot your root manager (following the root manager's uninstall instructions).
2)Flash a stock recovery (and stock kernel) from a stock ROM. Ensure the stock ROM you're using is the same build as what you're currently on. If you've flashed a custom logo.bin to hide the bootloader warning, you'll need a stock logo.bin.
3)Download and flash the OTA update in your stock recovery (should happen automatically).
4)Reboot into Nougat NPJ25.93-14.
5)Accept and download the March update, repeat the install.
6)Accept the June update if it's arrived for you (I've only seen the June update deployed in Brazil and India at the moment, other territories may have to wait), or download and flash the OTA update in stock recovery. The June security patch appears to only flash over the March update.
7)Once you're updated, flash TWRP and back up your entire system again (you may wish to flash a newer TWRP).
8)Flash ElementalX and your root manager as directed in the guides. Ensure the root manager you flash is quite recent - either SuperSU 2.79 SR3 or newer (2.82 SR1 is the latest) or magisk v12 or newer should be okay.
NOTE - you could skip steps 1-5 if you use fastboot and the commands in my previous post with the March 2017 fastboot ROM. You'll be flashing stock copies of the partitions to your device and bring it up to the March 2017 update in one go.
With 6.0.1, you could root after you flashed TWRP - on stock Nougat, the anti-rooting security is much stricter, and attempts to root with the stock (i.e. Motorola, hudsoncm) kernel may cause your device to bootloop. Thus, to get around those security measures, we can flash a custom kernel (i.e. a 3rd party kernel) that doesn't have that security. We have ElementalX v1.04 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 and vegito v6.08 https://forum.xda-developers.com/mo...ernel-vegito-kernel-1-0-13-september-t3461021 as custom kernels. To flash a custom kernel:
Download the stock version of the kernel (the LineageOS versions are for Lineage-based custom ROMs).
Reboot to TWRP.
Backup your boot partition (this contains your stock kernel)
Go back to 'Install' and tap the kernel zip
Follow the installer instructions to flash (e.g. with ElementalX, I've got stock 1561 MHz, no double tap to wake and none of the options selected on the installer screens).
Wipe cache/Dalvik
Reboot.
After flashing the custom kernel, then you can proceed to rooting on a Moto G4/Plus.

Here's what I ended up doing:
Updated using the March 2017 fastboot ROM and the instructions you provided.
Flashed the June OTA update files
Flashed the latest TWRP (3.1.1.0) over the stock recovery mode
Flashed ElementalX
Flashed Magisk 13.2
So I now have root access and my apps are still there. Unfortunately trying to install any modules in Magisk via the download section result in a "... has stopped working" message. I flashed the uninstaller and installed 13.1 but still no dice. The benefits of Magisk sounded great but I might just install SuperSU tomorrow instead.
I really appreciated your help, thank you very much

tekwarfare said:
Here's what I ended up doing:
Updated using the March 2017 fastboot ROM and the instructions you provided.
Flashed the June OTA update files
Flashed the latest TWRP (3.1.1.0) over the stock recovery mode
Flashed ElementalX
Flashed Magisk 13.2
So I now have root access and my apps are still there. Unfortunately trying to install any modules in Magisk via the download section result in a "... has stopped working" message. I flashed the uninstaller and installed 13.1 but still no dice. The benefits of Magisk sounded great but I might just install SuperSU tomorrow instead.
I really appreciated your help, thank you very much
Click to expand...
Click to collapse
No worries - if you're looking to switch to SuperSU, you'll need to uninstall magisk, then flash your clean stock kernel from your Nougat TWRP backup (flashing just the boot partition from the TWRP backup you made before flashing ElementalX should be okay). Then, you'll have unrooted and have a clean stock kernel - then flash ElementalX and SuperSU.
You'll need a clean stock kernel to remove traces of the previous root - you may have issues with SuperSU otherwise.

I think it was a problem with the way the zip files Magisk downloads are packaged, I can get them to install if I repackage the zip file.
Unfortunately, I never realised the xposed framework isn't supported on Nougat yet. I had a lot of quality of life tweaks that are greatly missed. Do you know if it's possible to safely downgrade back to Marshmallow at all?
I found this guide: https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201
But comments mention about future OTA updates maybe bricking the phone and "When come back from nougat to marshmallow don't flash gpt and bootloader , and flash everything else.".

Yeah, it might be that the modules haven't been updated for the latest magisk v13.2 yet.
Honestly, I do not know if it's safe to downgrade - with the June update, a critical security vulnerability was patch, and from what I've observed, attempts to downgrade have resulted in bricks. From what I understand, this seemed to result from users downgrading their GPT and bootloaders. You may be able to downgrade from Nougat to MM if you omit flashing the GPT and bootloader partitions (as mentioned in the guide you found), but there'll be a mismatch between your bootloader (Nougat) and your system (Marshmallow). Thus, for that reason, I'd suggest to not accept OTAs whatsoever. Again, I do not know if this is safe since the June update and I do not want to suggest things that might damage or ruin your device - it's your device, however.

SafetyNet Check Fails on Recently Unrooted Phone

unrooted XT1644 (previously Magisk rooted)
bootloader unlocked
TWRP 3.1.1-0
ElementalX kernel 3.10.84
OS version: 7.0
Security patch level: June 1, 2017, firmware NPJ25.93-14.5
Baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST
SafetyNet app failed "CTS profile" on unrooted Android. Oddly, my phone passed SafetyNet when I used Magisk. But after restoring my phone from a Nandroid backup taken before Magisk was flashed, it no longer passes. Might there be file directory remnants of Magisk that are affecting the SafetyNet result? Any troubleshooting steps appreciated.
There's now a September 1, 2017 OEM security OTA update waiting for me in my Notifications bar. I'm hopeful that the update will create a new system partition that'll get rid of what's causing the SafetyNet fail. Unfortunately a logo.bin TWRP flash fix made a change to my system partition settings that won't allow me to safely take an OTA update. The last time I flashed a security update was through the kindness of someone who provided a TWRP-flashable zip of the June 2017 NPJ25.93-14.5 OTA file. I'm hoping the same will eventually be provided for the September OTA update.

Same case with me too but I have model XT1643 (Indian Version), Build number: NPJS25.93.14-10.
Also, while booting up I still get bootloader unlocked warning and in Google Play Store it is showing Device Certification as Uncertified.
When I type fastboot oem lock in cmd bootloader slot count, bootloader slot suffixes and one more bootloader line all are showing not found.
And yes, in Bootloader Unlock warning it is showing 'ID: Bad key'
Other than this my device is working fine, IMEI numbers and Fingerprint sensor is working perfectly.
I followed guide by tywinlannister7: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please can anyone tell how can I correct it.

Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet. I am using a XT1642, I experienced this about a year ago when I was first experimenting with custom firmware.

I downloaded the September 1, 2017 security patch update but would prefer to flash it via TWRP instead of letting the system install it. However I can't even determine where it was downloaded to and I can't access the root directory anymore. Is it safe to manually flash it on an unrooted system containing TWRP, ElementalX kernel and the logo.bin boot screen fix? I'm especially concerned about flashing it on a system that doesn't pass SafetyNet.

TCUofficial said:
Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet.
Click to expand...
Click to collapse
Thank you for that essential information. I won't consider it a problem since the phone doesn't have NFC, so no Android Pay support anyway. However, I need some additional info before proceeding with the update.
Do I need to get rid of the ElementalX kernel and restore the original?
Do I need to undo the logo.bin bootloader unlock screen fix?
Do I need to get rid of TWRP before allowing the system to install the security patch?
Thanks.

Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?

mel2000 said:
Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
Answer is NO to both your questions. You need a STOCK boot image and a stock recovery image to “patch” (by which I think you mean upgrade via an OTA) your phone.

mel2000 said:
Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
In addition to zeomal's reply, your device would also need an unmodified system partition (no root, readonly, so no TWRP modifications) else the OTA will fail too.
Furthermore, I don't think the update you've downloaded is suitable for US retail devices, and if flashed might stop you from receiving future OTA updates. If you want the stock NPJ25.93-14.5 full ROM to revert to: https://androidfilehost.com/?fid=673368273298984458
Or the NPJ25.93-14.7 stock ROM: https://androidfilehost.com/?fid=817906626617945295 Of course, either of these will reset your device to stock, erasing TWRP, root and ElementalX and most likely your data, so back up. However, they should permit you to take OTA updates. Flash only in fastboot.
If you've already installed NPJS25.93-14-10, then you won't likely get the OTA update if installed on US devices.
As for SafetyNet/ device uncertified, I recall that's likely due to an unlocked bootloader. Magisk has the ability to hide the bootloader unlocked status from Safetynet, hence why when you removed magisk, the Safetynet detection saw your unlocked bootloader and therefore trips Safetynet. An easy way to get Safetynet passed is to reflash ElementalX and magisk.

I want to thank both zeomal and echo92 for their prompt and clear responses. I will address related issues before I move on.
EDIT: Used OEM Flash.bat to reupdate to June 2017 NPJ25.93-14.5, then allowed NPJ25.93-14.7 to be installed from Moto. All went well with an unlocked bootloader. Didn't lose any apps.
- TWRP (gone)
- ElementalX (gone)
- Logo.bin fix (gone)
- SafetyNet (failed - due to unlocked bootloader)
Thanks again to all.

[HELP] Stock ROM. Want to OTA but gpt.bin is a version ahead of everything else.

Long story short, didn't backup before everything, hard bricked with an OTA, recovered only by blankflashing and flashing the feb2018 gpt.bin (NPJS25.93-14-15) and then since I don't have the ROM for NPJS25.93-14-15, I flashed everything else from NPJS25.93-14-13.
Phone is working. Got TWRP in there, made a backup this time. Installing Magisk softbricks it, but that I'm trying to solve in another thread. Got the backup before trying to install Magisk anyways so I don't make it harder on myself to OTA.
I'd like to be able to do OTA updates, mainly due to the KRACK vulnerability that was solved with NPJS25.93-14-15.
The issue is: how do I get the phone back to the same version on everything? Afaik, I can't downgrade the gpt.bin to NPJS25.93-14-13 (when I try, I get the security downgrade error leading to a remote failure), which means I would have to bring everything to NPJS25.93-14-15 straight up? Can I do that without hardbricking again? As in, flash back the recovery from NPJS25.93-14-13 (the only thing that is not stock is twrp) and straight up do the update ignoring the fact that my gpt.bin is already from the version I will be updating to?
TL, DR Can a phone with NPJS25.93-14-15 gpt.bin and everything else NPJS25.93-14-13 make the OTA update to NPJS25.93-14-15? Can one downgrade gpt.bin somehow?

Did you find a solution for your problem? Maybe it's possible to flash all patched files manually to bring all to NPJS25.93-14-15??

1)If you revert back to NPJS25.93-14-13 fully, you should be okay to use the OTA update to NPJS25.93-14-15. This only will work as NPJS25.93-14-13 is the firmware directly preceding the Feb 2018 update. Using a firmware older than this may well cause a hard brick when you try to OTA update. However, you must fully re-flash or revert to a completely clean stock firmware build - no TWRP, no root etc. Unlocked bootloader does not matter. Easiest way would be to fastboot flash the stock NPJS25.93-14-13 ROM
2)Yeah, generally you cannot downgrade GPT or bootloaders - this is the underlying cause of bricks, as flashing old firmware results in applying old OTA updates, which corrupt your bootloader. However, in this case you're applying an OTA update that is as newer or newer than your existing system, so you should be okay.
3) You could in theory flash the Feb 2018 stock ROM - this is not been fully verified but some users have been able to successfully flash it. Verify this first before flashing: https://forum.xda-developers.com/showpost.php?p=75961872&postcount=716
4)Rooting on stock Nougat on our devices requires a custom kernel. Attempts to root on the stock Motorola Nougat kernel appears to trip anti-rooting protections and so causes the boot failures you've mentioned. You'll have to flash the stock firmware, apply the update, then flash/boot TWRP, then flash ElementalX (or another custom kernel) then magisk.

Holy cow @echo92, thanks so much for the detailed answer! I'll give this a try and update here with results.

Another soft bricked Moto g4 plus XT1642

Hi all,
So I am new to the game, I had an old(ish) phone and attempted to root the device. As some of you might have read on here before, I failed, I thought I had followed all the correct steps. I used the following steps as a guide: (from the unlockr). After attempting to install supersu I was left with a black screen. I can however access my recovery mode in bootloader, the thing is that bootloader is the only thing I can access. I cannot access my moto g4 plus via USB on windows, but for some reason I can access both internal and external memory on a mac. I can see the supersu version, my TWRP etc. I was wondering if someone could help me out, I know this has probably been posted before but I have not been able to find a possible solution as of yet. Thanks in advance

Is your device running stock Nougat (7.0) firmware? If so, then attempting to root on the stock Nougat Motorola kernel may result in a black screen and failure to boot, which appears to be what you've experienced. What those guides generally fail to mention (as they're quite old) is that rooting on the G4/Plus running Nougat requires flashing a custom kernel before you root. Failure to do so appears to trip the anti-rooting measures built into the stock kernel. A more recent guide that I've used for a stable root on a G4 Plus is this https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Bear in mind you do not need root to flash custom ROMs whatsoever, just TWRP.
If you can still access TWRP, you may have a way out. One thing to try is to flash a custom kernel onto your device - ElementalX is a good choice. https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX v2.0.1 for stock . Download the kernel to your computer, ensure your device is connected to your computer and booted to TWRP, and copy the custom kernel to your device. Try to flash the kernel and then see if your device boots.
If your device still fails to boot, you could try flashing the stock kernel from your backup (you did make a backup before rooting?) or if you're running a more recent OS build, I've uploaded the Feb 2018 and April 2018 security patch stock kernels here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M To flash this in general:
a)Download the kernel boot.img to your device.
b)In TWRP, tap Install.
c)Tap Install image at the bottom of the screen.
d)Navigate to where you downloaded the boot.img and select the image file.
e)Target the image to boot (not recovery).
f)Flash, and wipe cache.
g)Reboot and see if that works.
If those don't work, restore your backup if you made one or you may have to re-flash your stock firmware - you do not have to re-lock your bootloader or wipe your device with this re-flash of the stock firmware.
Does your Windows computer have the correct Motorola USB drivers installed on it? https://support.motorola.com/uk/en/drivers

Few questions before rooting/twrp

I just purchased the ph1 and plan on rooting the device and also flashing twrp. I've found the guides and everything seems pretty straight forward. The phone should be arriving tomorrow so at this point I'm unsure of the build it will have when I receive the device. I noticed a thread regarding the February update not working with twrp. Has this issue been resolved or will I need to flash to the January version to complete the task? Is the February and January builds mentioned the most recent updates for the device? I've found the links to the essential website but it gives me a error that its server IP cannot be found so I've been unable to check it. Is the site going to be down indefinitely due to no longer supporting the device? Does anyone have a link to the updates hosted elsewhere? The device was listed as GSM unlocked and did not mention any carrier tied to it so I'm assuming it's a factory unlocked device but will have to verify upon receiving it. Is the updates carrier dependant or do they all utilize the same files? Whats the consensus on roms/kernals on this device as opposed to rooting and using twrp on the most recent stock builds? Which Rom would you recommend if I do decide to go that route? Thanks for any advice you can offer, it's greatly appreciated.

Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?

SirDigitalKnight said:
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
Click to expand...
Click to collapse
I ended up receiving the device and it had Android 8 out of the box. I received a update that took me to Android 9 which was roughly 1100mb and another to Android 10 which was a little over 1000mb. The second update automatically included the February security patch. Rather than downgrade to January, I simply patched a February boot image with magisk and flashed with fastboot. I also flashed ElementalX kernel via fastboot. As far as I can tell they are not carrier specific. I am considering going to January now so I can use twrp to test some custom roms. For downgrading to January do I simply flash the January boot image which shows to be about 65mb or do I need to find the firmware in it's entirety? Also rather than down grade and use twrp can I just flash custom roms via fastboot? I would say you might have to downgrade to January to use twrp to flash Android 11 unless it's possible to flash the roms on fastboot, hopefully someone chimes in bc I'm unsure at this point.

Noob question, but what's the advantage to changing just the kernel?

Coming back to XDA after over a year. Realized Google Play Store update ruined my Magisk status, and evetually root (SafetyNet stuff). Here are some notes I took while I flashed in 2019, hope it helps.
1. DISABLE Security (PIN/Pattern/Fingerprint)
2. Backup Internal Storage
3. Boot to recovery TWRP, and backup nandroid.
(must go to bootloader and change slot to boot twrp.img flashed on that boot partition slot)
4. Normal boot and drag drop nandroid backup to PC.
5. Syncthing/Resilio for extra measure.
Have latest OTA.zip, boot.img (same version as OTA.zip), and latest Magisk.zip in root internal phone storage.
Have twrp.img in platform-tools adb root for flashing in fastboot.
twrp.zip is optional stored in root internal phone storage.
Flash OTA.zip update in TWRP. (assuming system is under slot_b)
This will flash to opposite slot, _a.
(I flashed under slot_b and new OTA went to slot_a, I booted back to _b and
old system version remained with broken Wifi becasue I accidentally flashed new boot.img in TWRP image over older system image
in slot_b, without the image flash, I suspect the old slot_b would have been perfectly untouched and rooted, as OTA applied to slot_a)
(Went back to A and new OTA was perfectly fine, although unrooted).
Boot to slot_a (system_a), make sure it runs good and verify version within settings, should be unrooted.
Boot to bootloader (under same OTA slot_a), default recovery should be stock recovery (droid logo) after OTA flash.
fastboot flash boot twrp.img (this will replace stock recovery to twrp recovery, deleting stock boot img as well, breaking OTA slot)
Reboot to recovery twrp (remain on same slot and will run off of RAM, leaving boot partition open to flash back stock boot.img)
Install boot.img (make sure version is correct) boot partition should be back to working condition although unrooted OTA system.
Try booting back to recovery on same slot, and stock droid recovery is back. (you cannot edit partitions from fastboot, hence twrp flip flop)
Try booting to system, it will boot but broken, no wifi. How? Not sure, maybe used old boot partition .img in slot_b to boot to system_a
Then flash latest magisk zip to patch stock boot.img for root.
(if you flashed twrp.img and magisk, then you're patching twrp, which is incorrect.
You want to boot to twrp, then flash boot.img back to boot_a partition, then run magisk.zip to patch stock boot.img in that boot_a partition)
Magisk.zip flash log:
Current boot slot: _a
Mounting system
Mounting vendor
Device is system-as-root
System-as-root, keep dm/avb-verity
Encrypted data, keep forceencrypt
Target image: /dev/block/sde11
Device platform: arm64
Constructing environment
Boot image is signed with AVB 1.0
Unpacking boot image
Checking ramdisk status
Stock boot image detected
Backing up stock boot image
Patching ramdisk
Repacking boot image
Flashing new boot image
Sign image with test keys
Unmounting partitions
Done
Updating partition details...
...done
Wipe cache/dalvik
In TWRP, tap reboot button and switch slot_a to other slot_b (older system version).
Reboot to bootloader_b in TWRP.
Flash twrp.img in that other old slot_b (For backup purposes and to have twrp at hand because boot_a has patched rooted boot.img and not twrp anymore)
Done!
Click to expand...
Click to collapse