Magisk needs to be installed after every reboot? - Xiaomi Redmi Note 5 Pro Questions & Answers

I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?

boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
Flash magisk v18.1 and it will work fine. Don't update Magisk. Some roms have this bug.

boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
If you reboot it should reappear (it does for me).
I don't know what's the root cause, I'll just wait patiently for a fix. Unfortunately I don't have time to troubleshoot or provide logs to whoever to help the investigation.
PS: in your description be more accurate "latest version of xyz" means nothing. Specify exactly which version. Especially there is stable and beta!

Related

[G4/G4 Plus] How to Install Magisk and pass safetynet?

Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do
mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
If I do a ROM update do I need to unSU and flash Magisk again?
Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.
aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?
guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.
Would using the wrong unSU version affect safetynet detection?
Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)

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.

Still able to use Google Play store and certify device after root + custom rom?

Hi,
Not too long ago a weird bug forced me to do a wipe of the device before i can start using it again (was all stock). Now i'm debating on a custom rom since the biggest obstacle for me (wiping the device and reinstalling everything again after) has been taken away.
I did however remember reading about devices with root and custom rom not being able to use the play store anymore since Google marked them as unregistered and such.
Is this still a problem? or is there a work around / fix for this to be found?
Thanks in advance.
DDakara said:
Hi,
Not too long ago a weird bug forced me to do a wipe of the device before i can start using it again (was all stock). Now i'm debating on a custom rom since the biggest obstacle for me (wiping the device and reinstalling everything again after) has been taken away.
I did however remember reading about devices with root and custom rom not being able to use the play store anymore since Google marked them as unregistered and such.
Is this still a problem? or is there a work around / fix for this to be found?
Thanks in advance.
Click to expand...
Click to collapse
Its not a problem if you flash custom rom + gapps + magisk altogether. Once all those files are flashed successfully then only reboot to system & your Google play store will say your device is certified.
abhishekjain.ims said:
Its not a problem if you flash custom rom + gapps + magisk altogether. Once all those files are flashed successfully then only reboot to system & your Google play store will say your device is certified.
Click to expand...
Click to collapse
Great thank you for your reply. Was losing hope i would not get an answer anymore.
Does this mean it's possible to use Google Pay with a custom rom? Or just the play store?
Edit: I think I have found my answer reading other threads, that it does work.
abhishekjain.ims said:
Its not a problem if you flash custom rom + gapps + magisk altogether. Once all those files are flashed successfully then only reboot to system & your Google play store will say your device is certified.
Click to expand...
Click to collapse
Alright so i have managed to install lineage and gapps, but somehow i cant get magisk to work.
1) can i just leave it like this without magisk and not have problems with google uncertified stuff?
2) if the above can't be done or if i can still somehow install magisk, please explain how. (i rooted one other time long ago with superSU, i dont have experience with magisk). I followed: https://www.xda-developers.com/how-to-install-magisk/ but i get an error 1 when trying to install in TWRP.
Please help and thanks in advance
DDakara said:
Alright so i have managed to install lineage and gapps, but somehow i cant get magisk to work.
1) can i just leave it like this without magisk and not have problems with google uncertified stuff?
2) if the above can't be done or if i can still somehow install magisk, please explain how. (i rooted one other time long ago with superSU, i dont have experience with magisk). I followed: https://www.xda-developers.com/how-to-install-magisk/ but i get an error 1 when trying to install in TWRP.
Please help and thanks in advance
Click to expand...
Click to collapse
To make magisk working properly just make sure you have /data partition EXT4 formatted also install this version of TWRP for Lenovo p2 https://androidfilehost.com/?fid=5862345805528044694 after that install latest version of magisk through recovery & you will be able to install magisk successfully.
anewman said:
Does this mean it's possible to use Google Pay with a custom rom? Or just the play store?
Edit: I think I have found my answer reading other threads, that it does work.
Click to expand...
Click to collapse
Correct. Even with Magisk root Google Pay and other secure banking apps work fine. You may just need to activate Magisk hide for certain apps.
abhishekjain.ims said:
To make magisk working properly just make sure you have /data partition EXT4 formatted also install this version of TWRP for Lenovo p2 https://androidfilehost.com/?fid=5862345805528044694 after that install latest version of magisk through recovery & you will be able to install magisk successfully.
Click to expand...
Click to collapse
Thank you for your reply.
Yes i did format the data partition to ext4. I used the TWRP version of their original website, searched for the lenovo p2a42 and found kuntao_row. (twrp-3.2.3-0-kuntao_row.img to be exact). Is there a difference in the version you linked there and this one ?
I currently have lineageos with gapps installed and working. If i am going to try and make magisk work. Are the following steps correct?:
1) install magisk manager
2) shut down and enter fastboost
3) flash different TWRP version
4) Boot into TWRP recovery
5) install magisk from ext sd
6) Then done? Or do i need to reinstall LineageOS and gapps again after those steps? And maybe wipe and reformat again at some points? if so, where?
Again thanks in advance and i really appreciate the help.
DDakara said:
Thank you for your reply.
Yes i did format the data partition to ext4. I used the TWRP version of their original website, searched for the lenovo p2a42 and found kuntao_row. (twrp-3.2.3-0-kuntao_row.img to be exact). Is there a difference in the version you linked there and this one ?
I currently have lineageos with gapps installed and working. If i am going to try and make magisk work. Are the following steps correct?:
1) install magisk manager
2) shut down and enter fastboost
3) flash different TWRP version
4) Boot into TWRP recovery
5) install magisk from ext sd
6) Then done? Or do i need to reinstall LineageOS and gapps again after those steps? And maybe wipe and reformat again at some points? if so, where?
Again thanks in advance and i really appreciate the help.
Click to expand...
Click to collapse
Just download latest version of the magisk, keep it somewhere in the storage then reboot to recovery, update your current recovery by the recovery I have given you above, reboot again to recovery then flash magisk & reboot to system. After successful flashing of magisk zip install magisk manager apk from play store or Google.
abhishekjain.ims said:
Just download latest version of the magisk, keep it somewhere in the storage then reboot to recovery, update your current recovery by the recovery I have given you above, reboot again to recovery then flash magisk & reboot to system. After successful flashing of magisk zip install magisk manager apk from play store or Google.
Click to expand...
Click to collapse
Perfect. Worked like a charm! Hero
So the TWRP version i used was the wrong one? Although it came from their website?
DDakara said:
Perfect. Worked like a charm! Hero
So the TWRP version i used was the wrong one? Although it came from their website?
Click to expand...
Click to collapse
Yes, the TWRP which I gave you is special. Cheers :good:
abhishekjain.ims said:
Yes, the TWRP which I gave you is special. Cheers :good:
Click to expand...
Click to collapse
Hi,
Back again haha. It still works properly and almost have everything set up as i wanted to. One more question arose:
The system is telling me there is a new version update for lineageos.
I am assuming i just click download on the latest version, then reboot into recovery (backup as optional), click install, search the zip and let it install then reboot again is the way to install it. But do i have to reinstall gapps? and does this process delete any data or is it just like a normal update and everything stays the way it was before installing the update?
Thanks again in advance.

Update magisk on a rooted P2XL with stock recovery

Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.
Or do I have to just ADB it ?
Also, is it better to just flash TWRP permanetly ?
Thanks
youssefkr said:
Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.
Or do I have to just ADB it ?
Also, is it better to just flash TWRP permanetly ?
Thanks
Click to expand...
Click to collapse
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is
Badger50 said:
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is
Click to expand...
Click to collapse
Now I'm more confused lol
Thanks for the answer though
youssefkr said:
Now I'm more confused lol
Thanks for the answer though
Click to expand...
Click to collapse
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.
Badger50 said:
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.
Click to expand...
Click to collapse
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever
youssefkr said:
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever
Click to expand...
Click to collapse
Congrats! Lucky duck. This issue is still perplexing me. The P2XL is just like a box of chocolates..."Ya never know what your gonna get" :laugh:
I'm having the same issue in beta Q 3.. everything I try to update it through magisk, it will not install at all.
Just get a error that reads, " app did not install".
Just updated yesterday to 19.2 through the manager yesterday. Running Q Beta 3. No problems.

Categories

Resources