Hi Guys
I'm with a problem. I installed Magisk a while ago and after my install Magisk just stopped working and it did not detect root (in Magisk manager). I reinstalled it and it worked...for 10min and after that it stopped. I update my rom (RR) which has Magisk preinstalled on it and still no succes. I flash the rom and after 10min Magisk stops working. I tried clean flashing rom but no succes.
Any suggestions guys?
Thanks
Unless you see any specific errors I TWRP Flash the latest version of Magisk.
... before that revert to a proper kernel IMG
How to install Magisk & Xposed? I keep getting bootloops.. "no digest file found"
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
I'm not sure about Oreo I think you can but you can't get certain modules or things like Xposed but double check that cuz I'm not sure
Secondly if you wanna flash 14.2 or 14.3 at the bottom of the magisk post where you download it will have the different versions to choose from any version after 14.0 supports the pixel
try flashing magisk by itself and see if that helps I know when I flash it with anything else it just doesn't show up and doesn't work but if you want when it bootloops flash the uninstaller and flash your boot image and that will fix the bootloop but do it again copy the log from twrp and put it on your computer and upload it here it will say exactly where it fails and what's wrong with it so we can help better
smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
blanken_ship said:
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
Click to expand...
Click to collapse
Thanks for the directions!
However, before I try this, I have one question... what is "VerifiedBootSigner-v8.zip"?
After searching, I see a bunch of information on the May security patch, but nothing talking about the August security patch (which is what I'm on). That being said, does it still apply?
You don't need Xposed, magisk has plenty of modules, but after rooting, flash the verified boot signer to allow for stock boot. It patches the boot image. Android 8 methods fixed this issue
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Mikkey81 said:
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Click to expand...
Click to collapse
WAAAAAAIIIIIT!!!! you need to be on Magisk 15.0 just failed multiple times and realized that was the last thing I Updated to 15.1..
Make sure you're flashing 15.0.
Can we get Xposed yet on Oreo with Magisk? I see it says there are 4 different options available in the module section of Magisk. One is labeled "Xposed framework". All the others are labeled "Xposed Framework SDK 25" down to 19. Which one should be used for Oreo?
So as yous would know there is a new magisk version, i update the app and randomly lose root then when I try and flash the new version via TWRP it causes my phone to boot loop please help
Bootlooped here too. Get into TWRP, Flash the uninstaller and install v16.
Edit: Clean installing v17 works too.
I got bootlooped too
Steps to install v17 without getting bootlooped:
1. Uninstall magisk with latest uninstaller
2. Wipe Cache/Dalvik
3. Boot into ROM
4. Reboot to TWRP
5. Install Magisk 17
6. Boot Into ROM, no need to wipe anything.
Thanks, you saved my life!
I am running stock(debloaded) 7.0 a320FL and advise against updating magisk to 17.X at all. After doing so(and getting past all the bootlooping) unlock screen is unresponsive. Currently sitting at latest 16.X magisk and intend to stay there for foreseeable future
I'm on oxygenos 5.0.5 and had Magisk 16.0 installed , I downloaded Magisk 17.0 and installed through twrp but phone went into boot loop , so I had to use Magisk uninstaller to get phone to start,
Now I dont have Magisk how go about installing it again
flash the v17 again .
i had the same problem , i downloaded the latest from github and flashed. everything is back to normal
Ok got magisk installed again , what caused the boot loop ? I thought flash through twrp was the safest option
I have OP3 and Lineage 14.1. I uninstalled magisk and reinstalled. Now I have root but no wifi. Do you have wifi?
Yes wifi is ok , but I just did a dirty flash of the rom , then installed twrp and magisk again
I'm try to magisk 17.1 no problem boot loop.
17.0 has bootloop bug on some phones it's fixed in 17.1
I need some help flashing the latest weekly miuimix a12. I'm experienced and all, been flashing roms before I could walk haha. But this device is really cracking me up.
I've tried flashing the weekly android 12 miuimix through twrp. Twrp vasishath gives a couldn't recognize zip file and twrp nebrassy gives a twrp crash (back to homescreen twrp) upon swiping the rom installation. I think both twrps don't allow installing android 12 rom. So I unzipped the latest weekly, went to fastboot and run the installer bat. This installed the rom for me.
But I don't think the installation was correctly done, since miuimix comes with magisk on board and magisk wasn't installed.
I also can't manually install magisk. I installed the app, patched the boot, flashed boot a and b, even installed twrp and sideloaded magisk.zip but the magisk app is showing n/a.
What did I do wrong, the miuimix a12 flashing or the patched boot flashing. Does someone know how to install an android 12 rom? This device is giving me a headache...
winesh said:
I need some help flashing the latest weekly miuimix a12. I'm experienced and all, been flashing roms before I could walk haha. But this device is really cracking me up.
I've tried flashing the weekly android 12 miuimix through twrp. Twrp vasishath gives a couldn't recognize zip file and twrp nebrassy gives a twrp crash (back to homescreen twrp) upon swiping the rom installation. I think both twrps don't allow installing android 12 rom. So I unzipped the latest weekly, went to fastboot and run the installer bat. This installed the rom for me.
But I don't think the installation was correctly done, since miuimix comes with magisk on board and magisk wasn't installed.
I also can't manually install magisk. I installed the app, patched the boot, flashed boot a and b, even installed twrp and sideloaded magisk.zip but the magisk app is showing n/a.
What did I do wrong, the miuimix a12 flashing or the patched boot flashing. Does someone know how to install an android 12 rom? This device is giving me a headache...
Click to expand...
Click to collapse
I'm not sure if magisk already support a12. The creator of magisk was working on it, with a lot of change like the no more hide feature, but idk if it already out
I was on the a12 supported canary build of magisk, but i guess maybe its to much "canary".
Or is installing miuimix a12 like i did, causing some trouble? By not being able tot flash the zip through twrp and installing with fastboot.
I'm lost on rooting my F3 on A12 as well. I can't do it through TWRP. I can't do it through adb sideload either. Will patching a boot image (not sure which to use for a global F3) and installing through magisk manager work?
Thanks.