Related
Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info
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.
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.
Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.
It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.
ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.
_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).
I've got an xt1768 RETAIL on npqs26.69-64-2 with bootloader unlocked. I flashed magisk, xposed system-less and the f2fs cache modules a while ago and just got the prompt for the new ota. I thought the update procedure was to disable magisk, reboot and then install the ota normally. After disabling magisk and rebooting the boot process gets stuck at "bad key", i assume because magisk modified one of the images. I'm able to get back into the bootloader and boot twrp and reflash magisk and everything boots up fine after. If anyone has a guide with the steps to actually do the update I'd appreciate it.
xeropressence said:
I've got an xt1768 RETAIL on npqs26.69-64-2 with bootloader unlocked. I flashed magisk, xposed system-less and the f2fs cache modules a while ago and just got the prompt for the new ota. I thought the update procedure was to disable magisk, reboot and then install the ota normally. After disabling magisk and rebooting the boot process gets stuck at "bad key", i assume because magisk modified one of the images. I'm able to get back into the bootloader and boot twrp and reflash magisk and everything boots up fine after. If anyone has a guide with the steps to actually do the update I'd appreciate it.
Click to expand...
Click to collapse
Well the thing is, you've modified your boot.img and unencrypted your device. So ota is not really going to work. Normally, you uninstall magisk and restore your stock boot.img, and if you've only booted twrp, you could take the ota. Did you also flash the no verity opt encrypt zip?
The problem is, when you flash the stock boot.img, your device is going to re encrypt as soon as you boot.
So you'll likely need the full firmware package to update. I do mine with rsdlite and the service file.xml within the full firmware when it becomes available.
Someone else may have better news for you, but I don't.
madbat99 said:
Well the thing is, you've modified your boot.img and unencrypted your device. So ota is not really going to work. Normally, you uninstall magisk and restore your stock boot.img, and if you've only booted twrp, you could take the ota. Did you also flash the no verity opt encrypt zip?
The problem is, when you flash the stock boot.img, your device is going to re encrypt as soon as you boot.
So you'll likely need the full firmware package to update. I do mine with rsdlite and the service file.xml within the full firmware when it becomes available.
Someone else may have better news for you, but I don't.
Click to expand...
Click to collapse
I did not flash the no verity opt encrypt zip, pretty sure magisk sets no verity by default as that setting is unchecked in the magisk manager. Device is still encrypted. It was my understanding that when using the restore image uninstall of magisk boot.img would be restored to its stock state, which leads me to believe that the system partition was modified.
xeropressence said:
I did not flash the no verity opt encrypt zip, pretty sure magisk sets no verity by default as that setting is unchecked in the magisk manager. Device is still encrypted. It was my understanding that when using the restore image uninstall of magisk boot.img would be restored to its stock state, which leads me to believe that the system partition was modified.
Click to expand...
Click to collapse
So you kept encryption too? Then you should be able to restore stock boot.img and take ota. Unless you have modified your system somewhere along the way. Magisk itself doesn't modify it.
Most are not able to get the phone to boot with encryption enabled.
So if you have not modified system at any point, then restoring the stock boot.img should have worked.
You can download the stock firmware that your device is currently on and flash the system.img and boot.img from it to be certain.
Edit:
Oohhh, it's not stuck at bad key, it just takes awhile to pass that. It's because of unlocked bootloader. Without a patched boot.img, it says bad key, but it should proceed after a minute or two. Sorry, just re read your first post.
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