Problem installing Magisk 20.2 on Galaxy S 7 Edge (Exynos) - Magisk

Hi,
On my phone, SM-G935G Galaxy S 7 Edge (Exynos) G935FXXU5ESD2 with TWRP 3.3.1 + Magisk 20.1 + Magisk Manager 7.4.0, I have no problem, but:
Update to Magisk Manager 7.5.0 = OK
Update directly to Magisk 20.2 (recommanded) = OK , no error message
Reload system & launch Magisk Manager = Magisk is not installed
Reload TWRP & install Magisk 20.2.zip = OK , no error message
Reload system & launch Magisk Manager = Magisk is not installed
Uninstall Magisk Manager + Magisk-uninstaller.zip in TWRP + reload system + Re-install Magisk 20.2 in TWRP + Magisk Manager 7.5.0 = Magisk is not installed
Reload TWRP & install Magisk 20.1 = OK , no error message
Reload system & launch Magisk Manager = OK , an update is available (20.2)
is there something I am doing wrong when I try to update to Magisk 20.2??
thanks for your help.

nenesse said:
Hi,
On my phone, SM-G935G Galaxy S 7 Edge (Exynos) G935FXXU5ESD2 with TWRP 3.3.1 + Magisk 20.1 + Magisk Manager 7.4.0, I have no problem, but:
Update to Magisk Manager 7.5.0 = OK
Update directly to Magisk 20.2 (recommanded) = OK , no error message
Reload system & launch Magisk Manager = Magisk is not installed
Reload TWRP & install Magisk 20.2.zip = OK , no error message
Reload system & launch Magisk Manager = Magisk is not installed
Uninstall Magisk Manager + Magisk-uninstaller.zip in TWRP + reload system + Re-install Magisk 20.2 in TWRP + Magisk Manager 7.5.0 = Magisk is not installed
Reload TWRP & install Magisk 20.1 = OK , no error message
Reload system & launch Magisk Manager = OK , an update is available (20.2)
is there something I am doing wrong when I try to update to Magisk 20.2??
thanks for your help.
Click to expand...
Click to collapse
With my Mix 3 everything went without problems.
Just stay with Magisk 20.1, report it in the Magisk bug tracker and wait for an update.
Gesendet von meinem MIX 3 mit Tapatalk

Same here on my S7 Edge.
I first updated the manager trough the manage itself, then magisk and installed using Direct Install (Recommended).
Installed fine, then I rebooted.
https://nsa40.casimages.com/img/2020/01/04/200104121818598848.jpg
Now it say Magisk is not installed, I downloaded the zip and flashed using twrp, but still same problem.
I also lost my root.

HTC u11
I have exactly the same problem on HTC U11 / leedroid rom...
Downgrade to 20.1...

Htc u11. Exact the same problem. I will downgrade, too.
MfG

HTC U11 ... the same
downgrade to 20.1

Same here

MattNCS said:
I have exactly the same problem on HTC U11 / leedroid rom...
Downgrade to 20.1...
Click to expand...
Click to collapse
I have exactly the same phone, same custom rom, and same problem.
How to downgrade btw? thanks!

namartlu said:
I have exactly the same phone, same custom rom, and same problem.
How to downgrade btw? thanks!
Click to expand...
Click to collapse
download magisk 20.1
github.com/topjohnwu/Magisk/releases/download/v20.1/Magisk-v20.1.zip
flash from Custom Recovery and everything will work again
i was having the same problem and solved by downgrading

I can only confirm the same problem occurs on my S8+ (Exynos).
Downgrading to v20.1 resolved issue.

HTC U11 with the same issue. Downgraded to 20.1.
I hate that notification that I need to update though...

Can someone confirm if v20.3 is working normally? Thanks.

It works.
At least on my Mi Mix 3 with xiaomi.eu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem MIX 3 mit Tapatalk

v20.3 is working correctly on my S8+ exynos.

Related

How to reset/erase Magisk configuration?

I was using Resurrection Remix 5.8.2 with Magisk v12 without problems, until I tried to pass the SafetyNET check. I read that "you have to enable Busybox", etc... and I did it in my phone. After restarting I've lost all the Magisk config and I can't find the options to rollback my changes:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried to wipe the data and cache of Magisk Manager in Settings ==> Apps ==> Magisk Manager. Reboot. Everything it's unchanged.
I've tried to wipe Cache and Dalvik & Cache from recovery. Reboot. Everything it's unchanged.
I've tried to unistall (with the Magisk uninstaller zip), reboot, wipe Cache and Dalvik & Cache from recovery. Reboot. Again in recovery flashed the Magisk v12 install zip, reboot and everything it's unchanged.
What should I do to reset/erase the Magisk configuration so I can start over from scratch?
ochoceros said:
I was using Resurrection Remix 5.8.2 with Magisk v12 without problems, until I tried to pass the SafetyNET check. I read that "you have to enable Busybox", etc... and I did it in my phone. After restarting I've lost all the Magisk config and I can't find the options to rollback my changes:
I've tried to wipe the data and cache of Magisk Manager in Settings ==> Apps ==> Magisk Manager. Reboot. Everything it's unchanged.
I've tried to wipe Cache and Dalvik & Cache from recovery. Reboot. Everything it's unchanged.
I've tried to unistall (with the Magisk uninstaller zip), reboot, wipe Cache and Dalvik & Cache from recovery. Reboot. Again in recovery flashed the Magisk v12 install zip, reboot and everything it's unchanged.
What should I do to reset/erase the Magisk configuration so I can start over from scratch?
Click to expand...
Click to collapse
Uninstall MagiskManager, then uninstall magisk. If it still fails, reflash your rom
veez21 said:
Uninstall MagiskManager, then uninstall magisk. If it still fails, reflash your rom
Click to expand...
Click to collapse
Thanks for pointing in the right direction. I've installed previously the Magisk Manager from the Playstore, but in the last version of the ROM Magisk Manager is included into Settings.
When I disabled it in Settings ==> Apps, it asked to revert to the ROM version, and I did it.
Then rebooted in recovery, flashed the uninstaller, reboot, reflashed the ROM again and everything is working.
Thanks a lot!
Didn't work for me
I tried your way and also the uninstall option in the app. Tried with disabled app (as you did) but nothing. When I open a particular app it tells that i cannot login cause my device is rooted. (Magisk Hide doesn't work)
Nucio said:
I tried your way and also the uninstall option in the app. Tried with disabled app (as you did) but nothing. When I open a particular app it tells that i cannot login cause my device is rooted. (Magisk Hide doesn't work)
Click to expand...
Click to collapse
That wasn't my problem. My problem was related to restore the original settings after a misconfiguration of Magisk. Your problem is to hide root to an app. Try to search another thread because this isn't related at all.

where is the menu in the magisk app?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ok since I upgraded my magisk version to v22, where are all the menus? I can't see where magisk hide and the module install menu are.
Please help
kaizx said:
View attachment 5244273
ok since I upgraded my magisk version to v22, where are all the menus? I can't see where magisk hide and the module install menu are.
Please help
Click to expand...
Click to collapse
It looks like it doesn´t display so it´s not properly installed?, other than the settings you couldn´t see the modules.
I installed it I've installed it properly, and yeah there are only settings menu
kaizx said:
I installed it I've installed it properly, and yeah there are only settings menu
Click to expand...
Click to collapse
I´m not referring to the app, it´s saying N/A. Follow the steps at the first option Magisk....Install and see what´s next.
ok now i can install it, but why my magisk app keeps crashing? I tried uninstalling the app and I installed the app manually, and the menu remains the same, no magiskhide and friends
I've tried installing and installing it again, but it's still like that
kaizx said:
I've tried installing and installing it again, but it's still like that
Click to expand...
Click to collapse
No, when you tap on Magisk install (not in app install) this will redirect to the methods available for your device either through Direct install or patching an image, did you try it?
Probably your device has some stuff with ramdisk partition so you have to update it manually through recovery.
The apk file since v.22.0 can be renamed from apk to zip and be installed through recovery also.
The magisk app looks like this
Then I opened it and there was a popup like that, and I clicked "ok"
He also downloads
But still the same, I've renamed it via twrp and installed it there at the same time.
SubwayChamp said:
No, when you tap on Magisk install (not in app install) this will redirect to the methods available for your device either through Direct install or patching an image, did you try it?
Probably your device has some stuff with ramdisk partition so you have to update it manually through recovery.
The apk file since v.22.0 can be renamed from apk to zip and be installed through recovery also.
Click to expand...
Click to collapse
How do I update it via recovery?
kaizx said:
How do I update it via recovery?
Click to expand...
Click to collapse
If you choose the option Direct Install Magisk will do it through recovery anyway as I mentioned you can rename the apk to zip and flash it through recovery too
I updated it and renamed it via recovery, but as you can see, my magisk keeps crashing
kaizx said:
I updated it and renamed it via recovery, but as you can see, my magisk keeps crashing
Click to expand...
Click to collapse
Then your device doesn´t support the latest version, you may uninstall it and downgrade it to v.21.4
yeah I thought so too, and thanks for the help

How To Guide [Guide] Update Oxygen Os (Stock/Root)

OnePlus Nord CE uses the update system offered by Google, instead of the standard one for the Oxygen Os, and this doesn't offer the possibilty to perform a local update. So I collect in a single thread the various options to update the phone from a full OTA file.
Here an index of full OTA: Repo of Oxygen OS Builds
How to update full OTA with OnePlus System Update​
Download and install [ApkMirror] OnePlus System Update and [Google Play] Activity Launcher (or any similiar app) since the OnePlus System Update is only accessible via an activity launcher.
Put the full OTA file in /storage/emulated/0/
From Activity Launcher search and launch the activity com.oneplus.localupdate.ui.home.HomeActivity.
Now that the updater has opened, you can update from a local file by clicking the settings icon at the top right.
Reboot.
How to update full OTA and keep Root​
Same procedure as above up to the #4 step, DON'T RESTART.
Go into Magisk Manager, select Install and Install to inactive slot.
Reboot.
How to update incremental OTA and keep Root​If the full OTA file is not available you can update normally with the system update by restoring the initial boot image first:
Go into Magisk Manager select Uninstall Magisk and Restore images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update from the system updater in the settings, DON'T RESTART.
Go into Magisk Manager, select Install and Install to inactive slot.
Reboot
Reserved #1
Reserved #2
It hasn't worked for me.
Now I don't get past the message: "this device has entered an unstable state..
Any idea what to do before trying unbrick tool?
sanangel said:
It hasn't worked for me.
Now I don't get past the message: "this device has entered an unstable state..
Any idea what to do before trying unbrick tool?
Click to expand...
Click to collapse
what update method did you use and what version did you install ?
Waleriks said:
what update method did you use and what version did you install ?
Click to expand...
Click to collapse
This.​​How to update incremental OTA and keep Root​If the full OTA file is not available you can update normally with the system update by restoring the initial boot image first:
Go into Magisk Manager select Uninstall Magisk and Restore images.
Update from the system updater in the settings.
Go into Magisk Manager, select Install and Install to inactive slot.
Reboot
sanangel said:
This.​​How to update incremental OTA and keep Root​If the full OTA file is not available you can update normally with the system update by restoring the initial boot image first:
Go into Magisk Manager select Uninstall Magisk and Restore images.
Update from the system updater in the settings.
Go into Magisk Manager, select Install and Install to inactive slot.
Reboot
Click to expand...
Click to collapse
I performed this procedure with my oneplus a few days ago, to update from the version 11.0.11.11 to the latest 11.0.14.14 without any problem.
Well, I've done something wrong and I'm going to have to pass the recovery tool...
I can't find com.oneplus.localupdate.ui.home.HomeActivity in the activity launcher. What am I doing wrong?
bossie1975 said:
I can't find com.oneplus.localupdate.ui.home.HomeActivity in the activity launcher. What am I doing wrong?
Click to expand...
Click to collapse
Found it. For me it was com.oneplus.opbackup.CheckUpdateActivity2
I succesfully upgraded to A12 in late october with the full OTA (with Root) option. Now I want to upgrade to the latest OTA update but I can't install OnePlus System Update nor find it in the Activity Launcher.
Does someone have a solution?
silberdavid said:
I succesfully upgraded to A12 in late october with the full OTA (with Root) option. Now I want to upgrade to the latest OTA update but I can't install OnePlus System Update nor find it in the Activity Launcher.
Does someone have a solution?
Click to expand...
Click to collapse
if it's an incremental update from the official updater just follow the section of the guide
How to update incremental OTA and keep Root

[Discussion] OP8Pro - magisk notification lead to unresponsive manager

Anyone else ever have it happen where you get a magisk update prompt, thought you swiped it away only to have accidentally tapped it? It installed something. But my magisk manager stopped responding. After trying to open it a few times, my 8pro rebooted. I had to install magiskv23.apk because my manager wasn't loading and it was renamed through the magisk app (I had to rename it because I had a couple apps that saw Magisk and wouldn't load). Now I'm stuck without root, and without a stock boot image for open beta 12. Pain in the rear situation. BUT TiBu still recognizes root access. So does terminal emulator when I type su. I get a pop up that MagixMgr isn't responding. Not even sure how to get out of this situation, since I don't have twrp..
If your talking about OB1 ColorOS12, you can download the OTA.zip for it, and extract the payload.bin file from the zip using 7zip (or similar). Run the payload.bin through the payload dumper tool to get the boot.img. Than patch that and flash it.
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
mattgyver said:
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
Click to expand...
Click to collapse
Where is open beta for oxygen os 12 on 8 pro? There were no news or release of an oos 12 ob...
@gsser It's not OOS 12. Open beta 12 is OOS 11. And it's been available since end of July.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought maybe reinstalling a patched boot image would help. Extracted my boot image, patched it in Magisk 23 apk. Flashed it in fastboot. Nada. Magisk 23 doesn't recognize magisk installed. my magisk app that was renamed through it's own UI still is failing to respond. Titanium Backup, Terminal Emulator, and Solid Explorer still all have retained root access.
I guess technically I'm fine, but I can't make changes to my modules, magiskHide apps, and I'm not sure if trying to upgrade to Magisk 24.1 apk will cause issues when upgrading my Magisk install.
What's interesting is that the magisk apk that my manager tried downloading was saved as Magisk-(-1).apk instead of any version numbering. it was only 280KB in size, compared to a few MB. and if I try manually installing it, it fails to parse the package.
Update1: so I flashed the official twrp beta. Downloaded the twrp app, and it never prompts about root permission, so it can't find my recovery. I don't get a prompt about MagixMgr not responding this time. So I can't grant any new apps root access.
Update2: apparently this has killed my wifi, too. I can't get the oneplus 8 pro to start wifi. it acts like it's starting, but if I swipe away the notification shade, and bring it back down, wifi is off again. i don't want to factory reset my phone, but I have this funny feeling that it's going to be my only option....
Update3: Uninstalled my magisk proxy app. pulled the full OTA OOS11 OB12 zip file and extracted payload.bin on my linux box. patched with magisk 24.1. flashed stock boot, and stock recovery to both a/b slots. then flashed magisk patched stock boot image instead of the one that I had pulled from my phone. success. Magisk 24.1 shows as installed, and I have full superuser access again. and a few more gray hairs. but all is well, even if I wasn't too sure about upgrading to the new magisk and losing magiskHide. but I'll look into the new modules being developed...

[Discussion] OP8Pro - magisk notification lead to unresponsive manager

Anyone else ever have it happen where you get a magisk update prompt, thought you swiped it away only to have accidentally tapped it? It installed something. But my magisk manager stopped responding. After trying to open it a few times, my 8pro rebooted. I had to install magiskv23.apk because my manager wasn't loading and it was renamed through the magisk app (I had to rename it because I had a couple apps that saw Magisk and wouldn't load). Now I'm stuck without root, and without a stock boot image for open beta 12. Pain in the rear situation. BUT TiBu still recognizes root access. So does terminal emulator when I type su. I get a pop up that MagixMgr isn't responding. Not even sure how to get out of this situation, since I don't have twrp..
If your talking about OB1 ColorOS12, you can download the OTA.zip for it, and extract the payload.bin file from the zip using 7zip (or similar). Run the payload.bin through the payload dumper tool to get the boot.img. Than patch that and flash it.
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
mattgyver said:
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
Click to expand...
Click to collapse
Where is open beta for oxygen os 12 on 8 pro? There were no news or release of an oos 12 ob...
@gsser It's not OOS 12. Open beta 12 is OOS 11. And it's been available since end of July.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought maybe reinstalling a patched boot image would help. Extracted my boot image, patched it in Magisk 23 apk. Flashed it in fastboot. Nada. Magisk 23 doesn't recognize magisk installed. my magisk app that was renamed through it's own UI still is failing to respond. Titanium Backup, Terminal Emulator, and Solid Explorer still all have retained root access.
I guess technically I'm fine, but I can't make changes to my modules, magiskHide apps, and I'm not sure if trying to upgrade to Magisk 24.1 apk will cause issues when upgrading my Magisk install.
What's interesting is that the magisk apk that my manager tried downloading was saved as Magisk-(-1).apk instead of any version numbering. it was only 280KB in size, compared to a few MB. and if I try manually installing it, it fails to parse the package.
Update1: so I flashed the official twrp beta. Downloaded the twrp app, and it never prompts about root permission, so it can't find my recovery. I don't get a prompt about MagixMgr not responding this time. So I can't grant any new apps root access.
Update2: apparently this has killed my wifi, too. I can't get the oneplus 8 pro to start wifi. it acts like it's starting, but if I swipe away the notification shade, and bring it back down, wifi is off again. i don't want to factory reset my phone, but I have this funny feeling that it's going to be my only option....
Update3: Uninstalled my magisk proxy app. pulled the full OTA OOS11 OB12 zip file and extracted payload.bin on my linux box. patched with magisk 24.1. flashed stock boot, and stock recovery to both a/b slots. then flashed magisk patched stock boot image instead of the one that I had pulled from my phone. success. Magisk 24.1 shows as installed, and I have full superuser access again. and a few more gray hairs. but all is well, even if I wasn't too sure about upgrading to the new magisk and losing magiskHide. but I'll look into the new modules being developed...

Categories

Resources