In a bit of a pickle with Magisk and Android 10 - Google Pixel 3 XL Questions & Answers

Okay here's what happened: I installed Magisk on Android 10 by patching the boot image and flashing from fastboot. This worked great. I installed a few modules, rebooting after each one to ensure it was still functioning. Then I got to a bad one (Riru EdXposed) and it stopped booting fully.
But now I can't disable the bad module to get just Magisk back. I can disable Magisk entirely by going to the old boot image but as soon as I boot a patched image to get Magisk back, the bad module is enabled and it won't boot fully.
Previously I would have used MagiskManager to resolve this from TWRP but TWRP is not released for Android 10 yet.
Any suggestions?

fysix said:
Any suggestions?
Click to expand...
Click to collapse
I believe this is the thread that explains what to do: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867

Exokan said:
I believe this is the thread that explains what to do: https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867
Click to expand...
Click to collapse
That looks like exactly what I need! I'll give it a try. Thanks!

Related

root with Magisk on Oreo.

I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?
humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.
Check out this post, it works like a charm.

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Pixel 3a XL Bootloop after enabling modules in Android 11

Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
scyther3989 said:
Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
Click to expand...
Click to collapse
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
adm1jtg said:
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
Click to expand...
Click to collapse
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
scyther3989 said:
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
Click to expand...
Click to collapse
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
adm1jtg said:
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
Click to expand...
Click to collapse
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
scyther3989 said:
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
Click to expand...
Click to collapse
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
adm1jtg said:
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
Click to expand...
Click to collapse
Yeah I'm hoping for some kind of insight on how to disable modules without root or maybe some new patch I haven't tried.
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
rifraf1 said:
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wow this actually worked!!
For anyone having a similiar issue:
I flashed the magisk_patched.img from Android 11 and let it go back into it's bootloop
As soon as the booting animation started I pressed volume UP and volume DOWN and it booted into safe mode
I restarted once I successfully made it into safe mode
The modules causing the bootloop were disabled and I am now able to have root in Android 11
Thank you @rifraf1

Question Stuck boot loop

Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Hunter_87 said:
Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Click to expand...
Click to collapse
you can try booting in safe mode, this will disable all magisk modules
Same issue tring to boot into safe mode
I just posted a tutorial to use adb to remove magisk modules for a situation just like this. worth to check it out if you can't get it done via safemode
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
there might be the same tutorial on xda but i had this copied to my clipboard
Scary that a detach module could cause bootloop...
Hunter_87 said:
Same issue tring to boot into safe mode
Click to expand...
Click to collapse
Did you able to make it work?
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Nothing.. i had to do an hard reset!! Thanks to all anyway..
Hunter_87 said:
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Click to expand...
Click to collapse
Have you removed all modules via abd?
netgar said:
Have you removed all modules via abd?
Click to expand...
Click to collapse
Nope, i tried with adb command as reported on linked guide but nothing happen and i receive just an error on cmd for too waitings.

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you

Categories

Resources