Related
Hi All,
Having a strange issue with Magisk.
I performed the upgrade today coming from renovate ice (Magisk module).
I followed the instructions of flashing the full OTA of the pie update. And then the blusparks TWRP. I rebooted into recovery and then flashed Magisk 17.1 as per the guide.
Booting back into the OS I can see that Magisk Manager is missing and my rooted apps are unable to get root either. Also when I try to goto the themes section inside settings the settings app crashes on me.
I attempted to reinstall Magisk but this did not work. I only noticed that when I was running the uninstaller for Magisk it did detect my boot image is Magisk rooted despite the OS not reflecting this.
Any ideas? My next step is 17.2 but I have my doubts on it.
EDIT: I tried 17.2 beta release and it made no difference. Exact same symptoms
spartan268 said:
Hi All,
Having a strange issue with Magisk.
I performed the upgrade today coming from renovate ice (Magisk module).
I followed the instructions of flashing the full OTA of the pie update. And then the blusparks TWRP. I rebooted into recovery and then flashed Magisk 17.1 as per the guide.
Booting back into the OS I can see that Magisk Manager is missing and my rooted apps are unable to get root either. Also when I try to goto the themes section inside settings the settings app crashes on me.
I attempted to reinstall Magisk but this did not work. I only noticed that when I was running the uninstaller for Magisk it did detect my boot image is Magisk rooted despite the OS not reflecting this.
Any ideas? My next step is 17.2 but I have my doubts on it.
Click to expand...
Click to collapse
Manually download and install magisk manager app then try to open root apps.
Then give root permission that works
pankspoo said:
Manually download and install magisk manager app then try to open root apps.
Then give root permission that works
Click to expand...
Click to collapse
It errors out saying "App not installed" when I try the manager APK.
spartan268 said:
It errors out saying "App not installed" when I try the manager APK.
Click to expand...
Click to collapse
Are u able to see magisk manager app in apps under sysytem apps?
If yes then remove or disable that
pankspoo said:
Are u able to see magisk manager app in apps under sysytem apps?
If yes then remove or disable that
Click to expand...
Click to collapse
Nothing there either...
pankspoo said:
Are u able to see magisk manager app in apps under sysytem apps?
If yes then remove or disable that
Click to expand...
Click to collapse
I was able to resolve the issue by performing a factory reset without having to wipe data. I'm guessing something old must have been left behind. Thanks for the help you provided, I appreciate it
Hi!
This morning I ran into some trouble while running the Android Q Open Beta rom that I've been using since release. I have downloaded and flashed the zip of the open beta with TWRP recovery and flashed Magisk afterwards. After the install was complete I booted in to Android Q and checked Magisk Manager to see if it installed correctly, which it did. I have some apps like Pokémon Go that require Magisk hide and they also worked fine for days. Until today, out of the blue Magisk Hide didn't seem to work anymore and those apps knew the devices was rooted.
I have then tried to:
1. reflash Magisk (although it was still installed)
2. reinstalled Magisk Manager
3. Reapplied Magisk Hide for those apps and rebooted
Between every step I also removed cache and data from the applications (even reinstalled), however I couldn't get the hide the root for the apps.
Anyone else encountered this? It's strange that it only failed after a few days of working on Android Q. Anyway I'm back on Android P at the moment.
Did you try updating magisk in magisk manager? I wasn't passing safety net until I did so
ConsoleHax said:
Hi!
This morning I ran into some trouble while running the Android Q Open Beta rom that I've been using since release. I have downloaded and flashed the zip of the open beta with TWRP recovery and flashed Magisk afterwards. After the install was complete I booted in to Android Q and checked Magisk Manager to see if it installed correctly, which it did. I have some apps like Pokémon Go that require Magisk hide and they also worked fine for days. Until today, out of the blue Magisk Hide didn't seem to work anymore and those apps knew the devices was rooted.
I have then tried to:
1. reflash Magisk (although it was still installed)
2. reinstalled Magisk Manager
3. Reapplied Magisk Hide for those apps and rebooted
Between every step I also removed cache and data from the applications (even reinstalled), however I couldn't get the hide the root for the apps.
Anyone else encountered this? It's strange that it only failed after a few days of working on Android Q. Anyway I'm back on Android P at the moment.
Click to expand...
Click to collapse
What version of magisk did you install? Try the magisk canary (debug) build. Works like a charm.
I got OOS update for OB5 (currently I'm on OB4). I am using systemize magisk module to systemize Google Phone app, to use Call Screening.
If I update the firmware to OB5, would I lose all this config and would need to start from scratch or can I retain this current setup?
Thanks in advance
raikkoni27 said:
I got OOS update for OB5 (currently I'm on OB4). I am using systemize magisk module to systemize Google Phone app, to use Call Screening.
If I update the firmware to OB5, would I lose all this config and would need to start from scratch or can I retain this current setup?
Thanks in advance
Click to expand...
Click to collapse
Disable all Magisk modules before updating and you can re enable them after the update is finished see this guide here for keeping root etc.
https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Hi,
with pleasure I share the module for center/right clock in the status bar, the module is created by @Tulsadiver, tested by me on Oneplus 7 Pro with firmware version as specified file name.
ESSENTIAL PREREQUISITE: BEFORE INSTALLING THE MOD, IT IS NECESSARY TO INSTALL, IF NOT PRESENT, THE "OVERLAY MOUNT FIX" MODULE BY @Zackptg5 DOWNLOADABLE FROM MAGISK MANAGER, WITHOUT THIS THE CLOCK MODULE WILL NOT WORK!
It is a magisk module and I want to repeat that it can only be used on Oneplus 7 Pro.
The module can only be used with the firmware release indicated in the file name, it will be my commitment to update the thread with the release of future updates.
I'm trying it and it doesn't seem to show any problems but I still recommend making a backup before trying it.
To remove the mod, simply uninstall the module using magisk manager or, if this is not usable, from recovery twrp, using the file manager deleting the module "OP7_VrThemer_OPSystemUI" that you find at the following path:
/data/adb/modules
Update: How to remove the module in case of failure (procedure valid for any magisk module):
Turn off the phone by pressing and holding the power button for a few seconds.
Turn the phone back on.
After the "Bootloader Unlocked" warning appears, press and hold down the "Volume up" and "Volume down" keys at the same time, until the startup animation appears.
The phone will boot correctly but will be operating in "Safe mode".
Now restart your phone normally.
The phone will boot in standard operating mode but with all magisk modules disabled.
Remove the magisk module that caused the problem and enable your other modules and reboot one last time.
The phone operating as if nothing had happened
My biggest, massive, THANKS go to @Tulsadiver, for sending me his xml file with the modifications necessary to obtain the movement of the clock and for passing me Its VRThemer module, without your help I could not have avoided the bootloop ... I can say that the mod is all from @Tulsadiver, the mod is all the result of his work and his expertise, I have only been a tester and shared his fantastic work with you.
Thanks also to @dladz, for giving me his support and advice!
Attention each module you find in this post is specific to the firmware indicated in the file name, with each new firmware it will be my concern to release the new updated module.
Flashing always at your own risk!!!
To be installed only with Magisk Manager, if installed by TWRP it does not work.
Please read all indications before proceeding with the installation, module has been tested and is working on the OxygenOS 10 and OxygenOS 11 based firmware, NOT tested with other firmware and non-OxygenOS based roms.
P.S. To complete the information, I have not had the opportunity to try the same module with other firmware versions, it could work but I have no way of knowing, if you decide to try remember that it should only be used on Oneplus 7 Pro with firmware OxygenOS 10 and OxygenOS 11 and that you do at your own risk. I test the module with the firmware specified in the file name before publishing it, if it is here for you it means that it has not given me any problems.
Flashing always at your own risk!!!
This sounds awesome. Thank you very much. I know it's a lot to ask, but would you be able to make a version that moves the clock to the right? That would be truly amazing if at all possible
a63548 said:
This sounds awesome. Thank you very much. I know it's a lot to ask, but would you be able to make a version that moves the clock to the right? That would be truly amazing if at all possible
Click to expand...
Click to collapse
Check your pm
You should post the right clock as well
Just a humble request, can you create a telegram group to support and test your module, it will be faster
a63548 said:
This sounds awesome. Thank you very much. I know it's a lot to ask, but would you be able to make a version that moves the clock to the right? That would be truly amazing if at all possible
Click to expand...
Click to collapse
mholloway said:
You should post the right clock as well
Click to expand...
Click to collapse
work in progress...stay tuned
Added to the first post mod for right clock and updated the module for center clock (if you want to update remove the old release, restart and install the new one).
I await your feedback.
Thanks to @Tulsadiver for his patience in supporting me and for his great availability!
New update of the "center clock" module, fixed clock displayed in the lockscreen defect, I recommend removing those installed up to now and replace with the latter released
Thanks for the mod. I tried the right clock mod but it did not work. Just to be fair, I tried on stable OS 10.3.5 and NOT on beta OS. Mod installed w/o any errors and I can see this mod installed in the Magisk Manager but clock is still on the left side. Rebooted twice, still no go. May be the beta 18 OS is the only OS that support this module. Keep up the good work. Thanks.
Gr8man001 said:
Thanks for the mod. I tried the right clock mod but it did not work. Just to be fair, I tried on stable OS 10.3.5 and NOT on beta OS. Mod installed w/o any errors and I can see this mod installed in the Magisk Manager but clock is still on the left side. Rebooted twice, still no go. May be the beta 18 OS is the only OS that support this module. Keep up the good work. Thanks.
Click to expand...
Click to collapse
Sorry my mistake, try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
The overlay mount fix module is necessary for the mod to work and I forgot to write it, sorry.
I await feedback
Installed right clock on beta 18,not working.
Magisk 20.04
Magisk manager 8.0.2
mholloway said:
Installed right clock on beta 18,not working.
Magisk 20.04
Magisk manager 8.0.2
Click to expand...
Click to collapse
Try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
I await feedback
dianoandr said:
Try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
Click to expand...
Click to collapse
That worked
mholloway said:
That worked
Click to expand...
Click to collapse
My mistake, sorry to you and everyone, I have the "overlay mount fix" module installed by default in my phone and I have not taken into account that it is necessary for the module to work...sorry again
dianoandr said:
Sorry my mistake, try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
The overlay mount fix module is necessary for the mod to work and I forgot to write it, sorry.
I await feedback
Click to expand...
Click to collapse
I know it worked for someone else but it really messed up my phone. Phone boots fine but screen is dark i.e. no display anymore. I am on OS 10.3.5 and the current Magisk 20.4. I'll use the fast boot zip when I get home to bring the phone back to life. Thanks!
Gr8man001 said:
I know it worked for someone else but it really messed up my phone. Phone boots fine but screen is dark i.e. no display anymore. I am on OS 10.3.5 and the current Magisk 20.4. I'll use the fast boot zip when I get home to bring the phone back to life. Thanks!
Click to expand...
Click to collapse
Go to recovery, with the integrated file manager function, delete the module "OP7_VrThemer_OPSystemUI" that you find at the following path: /data/adb/modules and reboot
dianoandr said:
Go to recovery, with the integrated file manager function, delete the module "OP7_VrThemer_OPSystemUI" that you find at the following path: /data/adb/modules and reboot
Click to expand...
Click to collapse
That did the trick. Thanks for your help. My phone came back to life and working fine
So, is it safe to say that right side clock module only work with OS 18 beta and not the latest stable OS 10.3.5?
Thanks again for your help.
Gr8man001 said:
That did the trick. Thanks for your help. My phone came back to life and working fine
So, is it safe to say that right side clock module only work with OS 18 beta and not the latest stable OS 10.3.5?
Thanks again for your help.
Click to expand...
Click to collapse
Happy it's back to normal, it's a trick to keep in mind for emergency situations.
The change itself is the same for all versions of oxygenos based on android 10, it probably changes something else in the apk and as a consequence the .xml file compiled with the mod, crashes your opsystemui.
I sent you a p.m.
I can confirm that mod works fine on Beta 19 as well? Thanks
Gr8man001 said:
I can confirm that mod works fine on Beta 19 as well Thanks
Click to expand...
Click to collapse
Great news, however as soon as I update my phone, I check that there are no major changes related to the apk and eventually update the modules to avoid instability.
I'm not able to open the Android camera app anymore. WIth Edxposed disabled it works. So I'm wondering if anyone on Android 11 Nov update with Edxposed has camera working. If so, could you kindly tell me your setup (ie. Edxposed version, etc.)?
Edit: It looks like the Camera update from Nov 17 is what broke this. After uninstalling the update it works.
I have the same problem - how did you uninstall the update?
EDIT: Nevermind I figured it out ?
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Anyone found a solution for this? Only stock version is working.
Apparently if you clear the cache/data of Google Play Services, the APK Mirror Installer will have better luck installing other versions.
jljtgr said:
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Click to expand...
Click to collapse
For pass the dread "verification did not succeed" message, clear your Google Play framework data. You will need to resetting some personalization settings (you will know when it happens) but install of 8.x camera app will work.
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
I have the same problem
neo_lithic3K said:
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
Click to expand...
Click to collapse
I tried it but it didn't work, it only works with v 21.3 but the modules stopped working. Hopefully a solution comes out.
Add gcam to black list and reboot. Just tried and it works
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
I tried updating Google Camera to 8.1, immediately didn't work as expected.
Added to Exposed blacklist, rebooted... still didn't work.
Added to Exposed Compat list, rebooted... still didn't work.
Downgraded to 7.1, works again.
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Added to Magisk Hide, Xposed Blacklist, Xposed Compat list, rebooted; installed 8.1.101.x... force closes immediately.
thx, it worked for me. I did it after I already installed 8.1
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
I did this except add to magiskhide and it worked.. uninstalled updates. Compatibility list camera app, rebooted then open it. After update back to 8.1. and opened camera..works great again
What fixed the problem for me was downloading the latest canary YAHFA build in exposed manager. And flashing it in Magisk. I already had configured the compatibility settings for the camera module.
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
This is all I had to do on my Pixel 4a 5G also. Thanks!
For anyone wondering, in EdExposed, if I go to XHide and hide camera it works. Hope this helps!
Hide camera in black list.
Latest version of exposed, riru, and riruedxposed June 21 update stock rooted. Working flawlessly
LSPosed is a better choice
EdXposed has not been updated for too long
Anyone found a solution? I can't get it to work hiding gcam on xposed blacklist and magiskhide