Related
Hey everyone,
Currently am running the Jan 5th OTA, rooted with magisk, using xposed, running the updated stock kernel and am on TWRP 3.2.1.
Should I be alright flashing the factory image with the -w removed? Could I just skip flashing the boot.img + flash the kernel seperately? Also, since TWRP recoveries are funky on Pixel atm, will this newest patch play nicely with TWRP?
Thank you in advance
I had issues booting twrp after sideloading the ota. Screen went black til battery died. Even after flashing twrp installer. Magisk wasn't installing via zip either
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
@TENN3R you did try unlock from twrp when you were all done?
I've dirty flashed like this before many a times... but now I can't decrypt data in TWRP 3.2.1.
I disabled password, did full ota script without -w and flashed twrp and magisk like normal, booted up and set the password. Done this a few times with different variables but nothing is changing the fact that twrp won't recognize the password while the system does.
Anyone else confirm working or not for them? Thanks.
TENN3R said:
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
Click to expand...
Click to collapse
pangolin.rollin said:
@TENN3R you did try unlock from twrp when you were all done?
I've dirty flashed like this before many a times... but now I can't decrypt data in TWRP 3.2.1.
I disabled password, did full ota script without -w and flashed twrp and magisk like normal, booted up and set the password. Done this a few times with different variables but nothing is changing the fact that twrp won't recognize the password while the system does.
Anyone else confirm working or not for them? Thanks.
Click to expand...
Click to collapse
If you removed lockscreen security you should not even get password in twrp, just main screen with wipe, flash etc..
Put your lockscreen security on "swipe" then check if lockscreen method effectively changed before going into twrp
Sent from my Google Pixel using XDA Labs
TENN3R said:
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux).
Click to expand...
Click to collapse
were did you find this factory image? I only see the ota-zip (pm: sailfish)
henk-jan said:
were did you find this factory image? I only see the ota-zip
Click to expand...
Click to collapse
https://developers.google.com/android/images
Section pixel sailfish, the latest 8.1.0 february
Sent from my Google Pixel using XDA Labs
TENN3R said:
https://developers.google.com/android/images
Section pixel sailfish, the latest 8.1.0 february
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
I know this site, but it's only the ota, not factory
Edit: I downloaded it again and now it's ok. Thanks
I think you misunderstood me. You used to be able to use your passcode to decrypt in TWRP (was fixed initially in 3.2.1).
After doing a FULL WIPE and fresh install without password, adding one after setup breaks TWRP decryption.
At this point unless someone corrects me with proof or a fix (I did a fresh install and it's broken) consider TWRP decryption broken again.
TENN3R said:
If you removed lockscreen security you should not even get password in twrp, just main screen with wipe, flash etc..
Put your lockscreen security on "swipe" then check if lockscreen method effectively changed before going into twrp
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
pangolin.rollin said:
I think you misunderstood me. You used to be able to use your passcode to decrypt in TWRP (was fixed initially in 3.2.1).
After doing a FULL WIPE and fresh install without password, adding one after setup breaks TWRP decryption.
At this point unless someone corrects me with proof or a fix (I did a fresh install and it's broken) consider TWRP decryption broken again.
Click to expand...
Click to collapse
OP started with: dirty flash the febr. OTA. So the answer is: no it can't without loosing TWRP. Is that right?
Seems so. The only way I can use TWRP atm is to disable any security/passwords etc.
henk-jan said:
OP started with: dirty flash the febr. OTA. So the answer is: no it can't without loosing TWRP. Is that right?
Click to expand...
Click to collapse
2x speed video of my using FlashFire to update the Pixel to the February Android 8.1 update, plus flashing ElementalX custom kernel v3.02 and Magisk v14.2: https://photos.app.goo.gl/4IVeBt8DFTQACHJi2
You have to be on Magisk 14.2 (not a higher version) to begin with, though, so if you're not, disregard this.
roirraW "edor" ehT said:
2x speed video of my using FlashFire to update the Pixel to the February Android 8.1 update, plus flashing ElementalX custom kernel v3.02 and Magisk v14.2: https://photos.app.goo.gl/4IVeBt8DFTQACHJi2
You have to be on Magisk 14.2 (not a higher version) to begin with, though, so if you're not, disregard this.
Click to expand...
Click to collapse
erm and what if we are on 14.3?
mark2410 said:
erm and what if we are on 14.3?
Click to expand...
Click to collapse
Since I haven't tried 14.3, if 14.3 doesn't work with FlashFire, then downgrade to 14.2.
TENN3R said:
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
Click to expand...
Click to collapse
Confirmed working on march update too :good:
Hey guys, I am using TWRP and I want to apply the Feb Patch/Image that was just released. The OTA won't work due to the fact that I am not running stock recovery I believe. So assuming I need to wipe the data and install the factory image from google how do I go about that? I'm familiar with flashing ROMs via recovery and the occasional sideload but that's about it.
Search the forum. It's been discussed multiple times.
Sent from my Pixel 2 using Tapatalk
BDragonD24 said:
Hey guys, I am using TWRP and I want to apply the Feb Patch/Image that was just released. The OTA won't work due to the fact that I am not running stock recovery I believe. So assuming I need to wipe the data and install the factory image from google how do I go about that? I'm familiar with flashing ROMs via recovery and the occasional sideload but that's about it.
Click to expand...
Click to collapse
Download the factory image from google. Extract it. Remove the -w option from the flash-all.bat script that is included with that download. Run flash-all and then re flash your kernel and magisk.
enzyne said:
Download the factory image from google. Extract it. Remove the -w option from the flash-all.bat script that is included with that download. Run flash-all and then re flash your kernel and magisk.
Click to expand...
Click to collapse
Great, that's the part I was missing. I took care of it and I'm good now. Thanks for the advice.
Hey guys, i used to have a Pixel 2 XL and Deuces always worked for me to install monthly updates, but this time i tried the same method and ended up with a corrupted Pixel 3, had to flash stock images to fix it.
What is the best method to install monthly updates on a rooted Pixel 3? Just edit the flass-all to remove the -w? Or is there an easier way such as uninstalling Magisk or something?
Cheers
Either flash-all minus the -w or sideload the OTA with stuck recovery. No other methods to keep data. If you are installing TWRP (and not just using the fastboot boot instance leaving stock recovery), then using the flash-all (minus -w) saves you from having to flash boot.img first to get stock recovery back. Either method will require you to re-root and reinstall TWRP.
sliding_billy said:
Either flash-all minus the -w or sideload the OTA with stuck recovery. No other methods to keep data. If you are installing TWRP (and not just using the fastboot boot instance leaving stock recovery), then using the flash-all (minus -w) saves you from having to flash boot.img first to get stock recovery back. Either method will require you to re-root and reinstall TWRP.
Click to expand...
Click to collapse
Thanks, so there is currently no way to just click "Uninstall" from within Magisk Manager and let the OTA install automatically, right? I read a comment in another thread in which the OP was trying to do that
luizffgarcia said:
Thanks, so there is currently no way to just click "Uninstall" from within Magisk Manager and let the OTA install automatically, right? I read a comment in another thread in which the OP was trying to do that
Click to expand...
Click to collapse
Could it be done? Maybe, but it would take just as much work. You would have to uninstall Magisk, TWRP, a kernel and possibly other things to get the OTA to auto-run and install properly. Then, you would have to deal with timing of the OTA showing up once you have "unmodified" the phone. OTA showing up is hit and miss. I have been doing it on both a Pixel and Pixel XL (and now P3/P3XL) since the OG was released 3 years ago. I have used OTA sideloads a couple of times when I want to force a slot change. The flash-all (without -w) is the fastest, most reliable method and requires no prework except for the -w text deletion. All of the work is on the backside. Fastboot flash TWRP, install TWRP, install kernel, root. PLus, all of your magisk hide settings are retained. You are just flashing Magisk package to bring back root. You have to do all of that with a true OTA or sideload OTA as well.
luizffgarcia said:
Thanks, so there is currently no way to just click "Uninstall" from within Magisk Manager and let the OTA install automatically, right? I read a comment in another thread in which the OP was trying to do that
Click to expand...
Click to collapse
Without TWRP it is possible, I have seen people do it but I have not.
Open Magisk and uninstall root, do not reboot.
Take the OTA, do not reboot.
Open Magisk and install but install to the inactive slot since that is what you will boot to after reboot.
Reboot and cross your fingers. Don't try this unless you are near a computer and ready to flash all minus the -w.
I still prefer the flash all method. Clean, easy, fast and never fails.
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This work for the Verizon Pixel 4 XL???
SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC
eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol