I was wondering can you update magisk through magisk manger or do you have to flash the zip over again Im not new to flashing updating but the Razer phone is so touchy and some things are different than other phones.thanks
I rooted my phone shortly after the Oreo update and have been updating magisk via magisk manager since.
I'm on magisk 19.1, manager is 7.1.2
SeriousFlash said:
I rooted my phone shortly after the Oreo update and have been updating magisk via magisk manager since.
I'm on magisk 19.1, manager is 7.1.2[/QUOTe.
Thanks for the reply works great and thank you again.
Click to expand...
Click to collapse
I may be being thick, but I can't see a way to update Magisk (not the manager) thru Magisk Manager?
Peace
That's how it looks for me. Always Magisk update on top and manager update below
I have an older version then maybe that won't allow update to Magisk ...
Related
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
phen0m2016 said:
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
Click to expand...
Click to collapse
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
computerslayer said:
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
Click to expand...
Click to collapse
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
phen0m2016 said:
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
Click to expand...
Click to collapse
Honestly, I'm not sure. I don't know if it is possible to upgrade between Android versions via OTA with TWRP installed - I vaguely remember some limitations on OTAs and TWRP. Best to check the official TWRP thread and the readme thread to be sure.
Similarly, I'm not sure about a clean install of Magisk. I've only been using it for about a month so I'm not confident in offering advice about uninstalling - especially since giving bad advice could end up with you not passing SafetyNet because I missed some basic step. I recommend checking out the Magisk forums.
I'm sorry I can't be of more help.
I installed an update to Magisk Manager to v5.9 via the Magisk Manager app. Then when I went back into Magisk Manager, I found that I had lost root (i.e. nothing shows up in the left drawer of the app and no root apps work). I tried flashing the Uninstaller.zip and reflashing TWRP and Magisk v16, but it still did not re-root my device. I'm running OOS 5.1.5 with Magisk Manager v5.8.3, and bluespark TWRP v8.69.
Hi
there is a new version of Magisk Manager (5.9.1) and after it will download the new version of Magisk 17.1 !
everything's ok for me on OB15
Rebel242 said:
Hi
there is a new version of Magisk Manager (5.9.1) and after it will download the new version of Magisk 17.1 !
everything's ok for me on OB15
Click to expand...
Click to collapse
You're right. Flashed v17.1 and now regained root access. Thx
It finally worked on mine (19.1).
Even it stated 4.2 may not support, I managed to:
Update to the last 2017 stock.
Install and run TWRP
Install Magisk and Magisk Manager and it shows latest version installed
That's it. I switched from SuperSU (no more development) to Magisk
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*
I own a firetv stick 2nd gen (tank). I have unlocked the device and installed the Prerooted rom which requires you to install magisk after you install the rom
I just cant figure out which magisk version to use. I have tested 25.2, 25.1, 24.3 but in all these versions the manager just crashing once i press any button on my remote (It doesnt open, it only shows the logo)
I tested 20.03 which luckily works and i had not got time to test any other versions, but i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Lenicyl said:
i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Click to expand...
Click to collapse
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Finnzz said:
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Click to expand...
Click to collapse
hey! For all the versions i installed (which is from the original magisk repo itself), i used the same apk to install both the manager and Magisk itself, so i dont think its signature
mismatch.
I was not aware of any custom magisk builds for firetv until i read your reply. I found this but this has the same issue as normal magisk, the issue being the Manager not working.
Also i just tested Magisk v22 and it works !!
Im thinking ill just stay on this version and i think ill be fine for now ?