Database Develop

Xposed framework not working on my Oneplus 5, Ressurection Remix V 5.8.4

I rooted my device,
And Installed the xposed application,
where I flashed the "sdk25 arm64" zip file.
{
"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"
}
If I open for let's say Snapprefs, It tells me the module is not activated
I activated the module and rebooted,
any help?

Jonathanve said:
I rooted my device,
And Installed the xposed application,
where I flashed the "sdk25 arm64" zip file.
If I open for let's say Snapprefs, It tells me the module is not activated
I activated the module and rebooted,
any help?
Click to expand...
Click to collapse
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.

fjsferreira said:
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.
Click to expand...
Click to collapse
I noticed that it tells me my phone is encrypted, any idea how to decrypt?
I tryed formatting data and reinstalling the ROM,
It seems it's encrypted by standard

fjsferreira said:
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.
Click to expand...
Click to collapse
Hello, I want to confirm that this was a temporary solution, It seems like soft rebooting device made it work,
thanks

I also use OP5 on stock Oxygen OS 4.5.10, Magisk 14 and systemless xposed 87.3 by topjohnwu. I have the same problem but it doesn't get fixed even if I soft reboot through the Material Xposed Installer app. What exactly am I supposed to do?
Στάλθηκε από το ONEPLUS A5000 μου χρησιμοποιώντας Tapatalk

Jonathanve said:
I noticed that it tells me my phone is encrypted, any idea how to decrypt?
I tryed formatting data and reinstalling the ROM,
It seems it's encrypted by standard
Click to expand...
Click to collapse
To decrypt you need to format data in TWRP then install a kernel that does not force encryption.

Face_Plant said:
To decrypt you need to format data in TWRP then install a kernel that does not force encryption.
Click to expand...
Click to collapse
Or you can run with FDE with: https://forum.xda-developers.com/showthread.php?t=3672477
You will lose the ability to boot unattended, so alarm when phone is off and scheduled boot won't work. And you'll have to format data too...
It's worth the inconvenience in my opinion. Been running this way for several days without any issues.
Full disclosure: I wrote the FDE conversion utility linked above.

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...

How do I install gapp's on A11 and with Chinese firmware version V5.17?

Hello friends!
I bought the Red Magic 3S. It has firmware from the Chinese version V5.17 and Android 11. I don't have Google play or Google Services. It also did not receive notification in most apps. I would like to know where to start, sorry for the bad english
As per "courtesy" a Senior Moderator translated your post, I encourage you to use a translator to use the English language in your later posts

Im in the same situation, installed the chinese version through system update. Updated chinese version to Android 11 V5.17. Installed TWRP with adb with bootloader and then also installed magisk through TWRP Recovery adb sideload but cannot install gapps pico it says error 70, when I googled that it means that theres not enough system storage to install gapps. I've deleted some of the original bloatware with magisk debloater and still has no space. I'm beginning to think that it is due to system being encrypted and twrp thinks theres no space to installed. Have tried removing screen lock still didn't work. Under settings security we can find were phone says encrypted I just have to figure out how yo decrypt. Maybe something nubia did to prevent us from rooting?

Try installing Google packages through the app called "HiGoPlay". You will find this app in the app center store
{
"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"
}
juan_carlos__007 said:
Im in the same situation, installed the chinese version through system update. Updated chinese version to Android 11 V5.17. Installed TWRP with adb with bootloader and then also installed magisk through TWRP Recovery adb sideload but cannot install gapps pico it says error 70, when I googled that it means that theres not enough system storage to install gapps. I've deleted some of the original bloatware with magisk debloater and still has no space. I'm beginning to think that it is due to system being encrypted and twrp thinks theres no space to installed. Have tried removing screen lock still didn't work. Under settings security we can find were phone says encrypted I just have to figure out how yo decrypt. Maybe something nubia did to prevent us from rooting?
Click to expand...
Click to collapse
In my case, I still haven't done any procedure, like unlocking the bootload, twrp, root, etc. But with you it can work!

if u still need help dm me

To install Оpen GApps pico on 11 android v5.17, you need to delete the folder nubia_Browser, it is in the folder app, this browser still needs to be removed so that it does not redirect to the Chinese store, you will have 100 mb of free space and twrp will not give an error that there is not enough free space.
https://sourceforge.net/projects/opengapps/files/arm64/20220503/open_gapps-arm64-11.0-pico-20220503.zip/download
Before installing google services, you need to remove all types of locks on your phone and put one pin code lock, then when you load it into the system, Google will ask for a pin code, then fingerprints: write your own pin code, fingerprints must be skipped!
Installing gapps pico:
1. You must be root!
2. reboot into twrp-3.3.1-4-NX629J-mauronofrio
3. click: settings
4. click: reset settings
5. go: extra
6. push: explorer
7. choose: system_root
8. choose: system
9. choose: app
10. find: nubia_Browser and other programs I threw off screenshots
11. in the lower right corner, click on the folder with a checkmark
12. click on: delete button
13. flash open gapps pico from phone memory or flash drive
14. reboot into the system.
15. optional: download Browser V7.3.5.2022091518a.zip, unzip and install browser apk.
SDCARD TRANSCRIPT:
The phone must be rooted with twrp-3.3.1-4-NX629J-mauronofrio installed!
1. In TWRP clear: Dalvik/ART Cache, Cache, Data, Device Memory
2. Reboot your phone in twrp
3. With flash drive install magisk Magisk-25.2(25200).zip
4. Reboot into the system.
5. Install Magisk 25.2.apk