Related
For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).
i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me
Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).
FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.
somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.
https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC
I tried to flash to magisk 19, 18, and 17 without success. I sideloaded and installed the newest april 19 security update OTA, I also grabbed the boot.img from there.
I tried using magisk manager to patch the image, I've tried using TWRP to install it to boot, as well as flashing with the zip... But both methods yields the same outcome, I get an infinite load (or boot loop ig?) and it won't work.
I flashed back to the original boot.img and phone works again. I also installed magisk 16.7 (by sideloading the zip) and my phone is now rooted again. Please help me, how do I use a later version of magisk (preferably the latest stable one)?
LootBoop said:
I tried to flash to magisk 19, 18, and 17 without success. I sideloaded and installed the newest april 19 security update OTA, I also grabbed the boot.img from there.
I tried using magisk manager to patch the image, I've tried using TWRP to install it to boot, as well as flashing with the zip... But both methods yields the same outcome, I get an infinite load (or boot loop ig?) and it won't work.
I flashed back to the original boot.img and phone works again. I also installed magisk 16.7 (by sideloading the zip) and my phone is now rooted again. Please help me, how do I use a later version of magisk (preferably the latest stable one)?
Click to expand...
Click to collapse
Try flashing the magisk uninstaller prior to flashing magisk.
Tulsadiver said:
Try flashing the magisk uninstaller prior to flashing magisk.
Click to expand...
Click to collapse
Thanks, that actually works.
https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
i did clean install of the recovery image this morning. all seems fine. nothing visually different
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
208.9mb too! Quite large for just a small incremental update too!
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.
Aren't you supposed to boot system before flashing magisk?
Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs
Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.
Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.
Anyone try to sideload the OTA? I believe the file is too big to sideload?
lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.
Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.
Link contains factory boot, and patched images, bootloader and radio from stated release
August 2020 (canary): https://drive.google.com/drive/folders/1SpBngNA35CnCCF57jK8wjhRUQEeyyCHG?usp=sharing
Tulsadiver module disabler: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867 (i think magisk canary disables modules if you boot into safe mode https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24 )
Way to update without flashing: https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md
here is a guide for getting root: https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
platform tools were updated in july 2020: https://developer.android.com/studio/releases/platform-tools
and a guide for google pay with root: https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248
Hide Google pay, Google play services, Google services framework, clear Google pay data after update and apply module.
old factory and patched images:
July 2020 (canary patch): https://drive.google.com/folderview?id=16-XxwJbT5VIIT1cbDTXIffdOuqwx3XCH
Feb 2020 (beta patch): https://drive.google.com/open?id=1WZ2-tza0IB3oICGFCHuj1GJKJr0nd8a3
Jan 2020 (canary patch): https://drive.google.com/open?id=1_zNt1i2uqbGhfEiWn0O716v9noJdR4uJ
Dec 2019(canary patch): https://drive.google.com/open?id=1JHc86ZOHkyNA0uJ6r43eLqG4oe6KBfGy
nov 2019(canary patch): https://drive.google.com/open?id=14GA7qrPITZ_-jYNDAFuC0bJiaKwGmqRP
oct 2019(canary patch) : https://drive.google.com/folderview?id=16bbXgyWwi8TmJNaih_UvdtXxB8fC5W0t
note: i think you can go into recovery mode to disable modules with canary magisk if you have trouble.
updated OP with nov images
one report of nov 2019 update breaking google pay
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
if you can push the magisk uninstall zip to your device, then fastboot booting into twrp then flashing the magisk uninstall zip that should do the trick.
swieder711 said:
The boot images are very helpful. Thanks!
I initially used the one patched for Magisk and was able to get root on the Nov release. Than I tried to install EdXposed Yahfa version (after installing Riru 19.5) and I got stuck in during boot at the "G logo" screen.
I was able to get back to a non-rooted system by reflashing the unpatched boot.img file. Now I need to figure out how to disable the Edxposed modules while staying on the November patch. The instructions for disabling Magisk modules seem written for a release earlier than Nov or they assume you have TWRP.
Any quick pointer on how to disable my Magisk modules on the November release?
Click to expand...
Click to collapse
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
jd1639 said:
See this, https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433. Twrp isn't going to work on 10.
Click to expand...
Click to collapse
Thanks for the pointer. I wasn't sure if that Disabler would work with the November image.
I ended up reflashing the factory default and than reapplying the correct files. I now have GravityBox running on the Nov Image!
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
ffchampmt said:
Up and running with OP's patched image and November "dirty" flash. Don't use G-pay so no report on that.
Edit - patched IMG after first boot shows magisk 19.5 installed, not 20.2 ¯\_(ツ)_/¯
Click to expand...
Click to collapse
OP updated to show 19.5.
Had the same issue and ran into the problem getting the modules disabled. Glad you were able to get it up and running.
Sent from my Pixel 3 XL using Tapatalk
i think doing a full uninstall of magisk (removes modules and settings) might be best until twrp or something else comes along...
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
chinesecooler said:
Thanks for the patched image @dipstik. Gonna wait for Dec's iteration
Click to expand...
Click to collapse
wait no more!
Woop woop, time for my bi-annually update
dipstik said:
wait no more!
Click to expand...
Click to collapse
Which version of Magisk did you use to patch the boot image? I tried using stable and canary to patch the stock boot image when I updated earlier, but each time it would just reboot straight to bootloader.
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
dipstik said:
i patched with 20.2-72edbfc4 .
this thread might help. i havent updated yet. https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605
Click to expand...
Click to collapse
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Face_Plant said:
I've been following that thread and there doesn't really seem to be a definitive solution yet. What works for one person doesn't seem to work for anyone else (including me). I'll just live without root for the first time in about 9 years until the problem is figured out...
Click to expand...
Click to collapse
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
comady25 said:
Is root working for anyone else on the Dec update? I just flashed it and Magisk detects that it's installed (20.2 so I'm guessing it's Canary as the latest stable/beta is 20.1) but no root apps work at all.
Click to expand...
Click to collapse
It is working for many and not for others. My wife's P3 rooted fine with canary.
jlokos said:
I read through this thread and the other thread you referenced, Has anyone tried topjohnwu's method: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md ? I used with the November update and had no issues. It doesn't involve flashing patched image.
Click to expand...
Click to collapse
I used this method and it worked with no issues. It was only the second time i used this method but with others having issues with the factory image and patched boot image i thought I'd give it a try.
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,