Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Very strange, but it just worked, after the 20th time of doing the same thing. Who knows why
Hey, my issue with Magisk is a bit different. I've upgraded my Pixel 2 XL every month and flashed Magisk afterwords. What I keep running into for the past couple of months is that after I'm all done, I will get a notification that there's an update to Magisk, but it's the same version I already have. I've tried different versions from 16.7 to the beta 17.3 and I would always seem to lose root after a while and be prompted to download the update to Magisk. Any help is greatly appreciated! Thanks in advance.
I am having the same issue with magisk after updating to nov update. Did the flashall then booted twrp and flash magisk Not sure why
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Run the Magisk uninstaller first
run 17.1 or the uninstaller. i've had better luck with 17.1
I guess the issue is linked to the Active Edge Module!
Download "uninmod_magisk", install it via TWRP, execute it via Terminal in TWRP, delete the Active Edge Module.
Now you can boot and reinstall that module.
Related
So I was on rooted 3.2.6 with xposed installed and decided to upgrade to 3.2.8.
I dirty flashed the full ROM 3.2.8 onto my 3.2.6 (without flashing SU or xposed because I wanted to use Snapchat with snapprefs again so I i flashed 3.2.8 without root , logged into Snapchat etc. )
after that I flashed superuser and xposed and since then my phone doesnt boot.
I interrupted the first try because it took over 20 minutes then tried it again after clearing cache and dalvik but it still doesnt boot ( i see the two circles and red dot)
Hope someone can help me
PS: I didnt make a backup because it would be too large, on the other hand I have the full 3.2.8 on my internal storage as well as the latest superSU
solved it
If someone experiences the same problem you need the newest xposed version v87. Flash it normally and wipe cache/dalvik , thats it !
I had that, I fixed it by boot to twrp flash the xposed uninstaller zip to remove xposed, then the phone should boot normally, I then found a newer version of xposed (the November security patch in 3.2.8 doesn't like older versions) and flashed it via twrp again, all my modules were still there and didn't need setting up again either.
Hope that helps
J_The_Nerd said:
I had that, I fixed it by boot to twrp flash the xposed uninstaller zip to remove xposed, then the phone should boot normally, I then found a newer version of xposed (the November security patch in 3.2.8 doesn't like older versions) and flashed it via twrp again, all my modules were still there and didn't need setting up again either.
Hope that helps
Click to expand...
Click to collapse
thats exactly what I did and it works perfectly now. Thanks.
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?
Pixel XL running 8.0.0 OPR3.170623.007, developer options and USB Debugging are both on.
I was rooted for a while now, then I tried using one of my root-only apps and it told me it can't get root access.
I looked for SuperSU, which was missing.
I unrooted and rerooted using Skipsoft Unified Android Toolkit.
It flashed SuperSU 2.82 and flashed TWRP 3.1.1.1. The TWRP flashed just fine, but no matter how many times I flash SuperSU, it doesn't show up in my app drawer and the phone is still not rooted. I tried SuperSU 2.82 and the SR5 stable beta, neither worked. I also tried installing it through the Play Store after flashing it, it goes through the install process then just give me the option to install again, never fixes my issue.
Any idea on what I can do next?
edit: I updated to 3.2.0.0 and was able to root. Flashing the most recent beta and non-beta Magisk versions did not work, neither did installing the SuperSU APK. Once I updated to 3.2.0.0 I was able to root with Magisk just fine.
Flash the stock boot.img to both slots and reroot. Use SR5.
I would also advise to start by flashing the stock boot image. I would then boot twrp, flash twrp, then flash latest su.
If that doesn't work I would try going with the latest magisk zip (14.5)
I should have mentioned this, Unified Tool Kit flashed the factory boot image before releasing the latest TWRP and then flashing the most recent SuperSU. I did try flashing SR5 with negative results.
I'll give Magisk a try.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I followed 1,2,3,4,8, zero issues on 8.1.
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
DeviceManagent said:
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
Click to expand...
Click to collapse
Common issue. You can grab the app apk from inside the zip and install it.
I tried flashing both beta and non-beta Magisk versions and installing the SuperSU APK, nothing worked.
I saw that a new TWRP got released, 3.2.0.0. I flashed that and was able to successfully root. Thanks for your help, guys.
Hi all,
I'm on the November update, rooted still with stock recovery, magisk 17.3, custom kernel, substratum and a few modules installed via magisk.
to get the December update installed, I am trying to figure out best way. Do I download the December update, then unzip to my adb folder where all tools are installed. Then, flash the update removing the "-w" to maintain data. Then, without rebooting, flash the twrp image, then magisk?
TheFuzz said:
Hi all,
I'm on the November update, rooted still with stock recovery, magisk 17.3, custom kernel, substratum and a few modules installed via magisk.
to get the December update installed, I am trying to figure out best way. Do I download the December update, then unzip to my adb folder where all tools are installed. Then, flash the update removing the "-w" to maintain data. Then, without rebooting, flash the twrp image, then magisk?
Click to expand...
Click to collapse
What you described is how I plan to upgrade. Clean install with -w removed. I made too many tweaks to try and unwind them manually (TWRP, Magisk, custom kernel, Tulsa mods, etc).
swieder711 said:
What you described is how I plan to upgrade. Clean install with -w removed. I made too many tweaks to try and unwind them manually (TWRP, Magisk, custom kernel, Tulsa mods, etc).
Click to expand...
Click to collapse
I've had some issues with some of the mods I've done so I'm thinking better to start fresh and build back what I like. I looked over the thread on how-to root pixel 3 with magisk and seems like following the first part, covering "if coming from rooted September software guide" seems the logical directions to follow?
Answered my own question with the incredible help of the how to guide!
Removed the -w did not uninstall any mods at all, left my phone exactly as it is on November update with all my themes and modules installed.
Flashed the update in fastboot, rebooted to operating system
Went back into TWRP img and flashed magisk 17.3 and rebooted. Everything was still on device and magisk modules were still working
Had to reinstall substratum theme which was a good thing because I had messed up a few things.
Flashed @Tulsadiver mods for home screen no search and app drawer, rebooted and all is good!
Off topic but can't find any information. Can you uninstall substratum themes from manager? I can't on mine. Same exact setup.
After updating to this firmware I lost root. So I tried as usual to flash via fastboot twrp-3.6.0_11-0-I001D.img and then in recovery magisk 23.0 (24.1 makes twrp crash). When I reeboot into system (after clearing dalvik/cache) magisk is not installed, although the flashing of the zip in recovery was flawless. i even reflashed the stock rom+magisk (losing the twrp recovery) but no way magisk was there.
With the previous rom versions nevere had this problem. Is it a trick og the new rom to prevent from rooting? Any idea? Suggestions?
fux1976 said:
After updating to this firmware I lost root. So I tried as usual to flash via fastboot twrp-3.6.0_11-0-I001D.img and then in recovery magisk 23.0 (24.1 makes twrp crash). When I reeboot into system (after clearing dalvik/cache) magisk is not installed, although the flashing of the zip in recovery was flawless. i even reflashed the stock rom+magisk (losing the twrp recovery) but no way magisk was there.
With the previous rom versions nevere had this problem. Is it a trick og the new rom to prevent from rooting? Any idea? Suggestions?
Click to expand...
Click to collapse
so...basically, you are unable to root using either the TWRP or simply Magisk?
What version of Magisk were you using?
I am thinking of updating but I need root access so the situation you are facing is worrisome to me.
ausaras said:
so...basically, you are unable to root using either the TWRP or simply Magisk?
What version of Magisk were you using?
I am thinking of updating but I need root access so the situation you are facing is worrisome to me.
Click to expand...
Click to collapse
I updated to the latest version and as always installed magisk to the inactive slot before reboot. Update was fine and root intact.
I was on magisk 24.1
gilsol said:
I updated to the latest version and as always installed magisk to the inactive slot before reboot. Update was fine and root intact.
I was on magisk 24.1
Click to expand...
Click to collapse
Thank you very much for sharing. This puts my mind at ease.
I will update when I find the time.
Thanks, again!
jb
*issue resolved*