I have rooted my Pocophone with Magisk and I have installed some magisk modules. Also, I have enabled 60fps video recording with the Helper app. However, I have kept stock recovery.
In order to update to the next stable OTA without any bootloops or data erased, is it enough to simply Uninstall Magisk and then install the OTA inside the Updater app? Will the Helper mod for 60fps cause any problems?
Related
Hello,
What would be the 2019 cleanest way to uninstall a system app?
My case: Flashed xiaomi EU (clean) ROM for a Redmi and it didn't come with youtube preinstalled. I ran to install it but now I noticed it cannot be uninstalled normally, only remove system updates (this one is funny because I assume removing system updates leaves a base version but not sure what a base version of youtube would be for a ROM that didn't have it in the first place, I guess youtube base version would be related to playstore version installed).
So I've seen uninstall procedures via ADB, titaniumbackup (don't own it yet) and other playstore apps. But not sure what would be the most recommended method nowadays, on a rooted phone (magisk) if that makes any difference.
Thanks for your time
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
Newest Magisk, I installthe module, reboot and is not being activated. Thus, adaware not working and getting a ton of ads in everything (apps and browser). Am I the only one?
Picture attached is after installing the module and rebooting.Tried removing, re-enabling, must have restarted a hundred times!
dreamdrake said:
Newest Magisk, I installthe module, reboot and is not being activated. Thus, adaware not working and getting a ton of ads in everything (apps and browser). Am I the only one?
Picture attached is after installing the module and rebooting.Tried removing, re-enabling, must have restarted a hundred times!
Click to expand...
Click to collapse
working fine for me on 11.0.4 havoc os 3.2
Thank you for the information..
Anyone else on the global stable rom? It was working before the update to the new rom and Magisk. What might have broken it?
Working fine on 11.0.4. miui and magisk canary 20,4
SOLVED
I set Magisk Core only to off in settings and everything works now. Thanks to all for your help and input.
I tried to install youtube vanced and now I can't install any apps from any place( including the google play store), I have not yet attempted using twrp to install an apk but I rather not. Is there any easy fix to this? last time this happened I believe I flashed a new rom. Currently I'm on stock oreo and don't have any Xposed modules installed. Ugh I don't have to reinstall everything. I'm getting a new phone soon and this will soon be a play phone.
Try reflashing the TWRP-flashable zip for the last Oreo, then reflash Magisk.
Then clear caches and reboot.
If you try YouTube Vanced, use the older one.
I can run any custom ROM but when I root with magisk, I get the camera error/black screen from Snapchat or just trying to take a regular picture with gcam.
Is this because the root was detected? Would it be better to root a non Google ROM and flash gapps?
That sounds like its got to be a coincidence.
Try grapheneos. If you need gapps, they have a very specialized sandboxing system to protect your data from gapps invasiveness.