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.

[Guide] PROJECT TREBLE for ZOOM

{
"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"
}
So, we have a fully functional TWRP. Now we can install custom firmware. I've been trying to get a working system on the Project Treble firmware for a long time, and found the right a working GSI images!
The firmware was taken as an example for installation Havoc-OS 3.5
Prerequisites - bootloader must be unlocked, clean Stock firmware must be installed.
Installation Instruction
1. Download the Project Treble system image archive without included GAPPs (Vanilla, ARM64-AB). Otherwise the system will not start. Unpack the archive and copy the ROM image to an external SDCard.
Download and copy to external SD Card GAPPs archive (ARM64, Android 10), Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4) and Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ), Permissiver_v4 (look at the attached files);
2. Install TWRP according to the Instruction, doing everything up to the 6th step.
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Project Treble system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. Installing GAPPs. If you try to install the GAPPs archive immediately, the installation will be aborted with an error: 70 (Error 70). This will be eliminated as follows:
- Go to the "Wipe" tab;
- Then select "Advanced Wipe";
- In the menu that opens, select the System partition and click "Repair or change file system";
- A few buttons will appear and click "Resize File System". If the process failed the first time with Error 1, then repeat this action again.
Now you can install the GAPPs archive without any errors.
6. When the installation is complete, go to Wipe and perform a "Swipe Factory reset".
7. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, do not worry.
Important additions
Adaptive brightness - Copy framework-res__auto_generated_rro.apk to /vendor/overlay. Give this application permission 644. Remove the "FrameworkResVendor" folder from /vendor/overlay. Reboot the phone. In "Phone Settings" you will have a new item "Adaptive brightness" and this feature will work in "Quick Settings".
Noticed problems on Havoc-OS 3.5:
- Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated.
- Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
- Unlocking by fingerprint is implemented for scanners on the back of the phone.
Automatic brightness setting does not work - Fixed!

Found working Project Treble firmware:
Havoc-OS-v3.5 https://sourceforge.net/projects/ha...fficial-arm64-ab-vanilla-nosu.img.xz/download
AOSP 10.0 v216 https://github.com/phhusson/treble_...oad/v216/system-quack-arm64-ab-vanilla.img.xz
Firmware installation instructions will be available later.

It's truely impressive what you are doing!

Wooooooow! Finally!

Awesome work!!!
Can you confirm if the fingerprint scanner works with any of the roms?
Or if there is something missing?
Also whichone would you recommend over stock?
Thanks!!!

One zoom
Can we install this project in our one zoom?

spcarlos2 said:
Can we install this project in our one zoom?
Click to expand...
Click to collapse
I don't understand the question

ilia3367 said:
I don't understand the question
Click to expand...
Click to collapse
can i install this rom on my one zoom cell phone?

spcarlos2 said:
can i install this rom on my one zoom cell phone?
Click to expand...
Click to collapse
Buddy! And for which phone is this theme created? Isn't it for Moto One Zoom? :laugh:

After the flashes I get this:
Failed to mount '/system's (Invalid argument)
After I unpack the image zip, I rename to .img, maybe that's why, help me please...

After a successful installation, I reboot the phone and don't starts, just go to TWRP over and over, what should I do?...

thirdphotographer said:
After a successful installation, I reboot the phone and don't starts, just go to TWRP over and over, what should I do?...
Click to expand...
Click to collapse
Install again Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip.

I'm assuming there would be no way to get Google pay to work with this if it doesn't pass safetynet?

Afifus said:
I'm assuming there would be no way to get Google pay to work with this if it doesn't pass safetynet?
Click to expand...
Click to collapse
https://4pda.ru/forum/index.php?showtopic=968480&view=findpost&p=96932663
Try to read with a translator.

[HELP] Storage is full on Google Play but system has access to app-lib

Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
{
"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"
}
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!

Possible solution
Jandresgomez said:
Hi, this is my first time rooting and android phone, so please excuse me if this sounds like a dumb request. I've been going about this for almost 2 days and ran out of options. First off, here is what I'm using:
- Redmi S2
- Android 9
- Root: Yes, Magisk 20.4
- MIUI 11.0.2 stock (flashed after I wiped system data by accident before my first backup)
So, my issue is the following: whenever I try to install an app through google play or attempt to download a Magisk module, the system fails to do so. In particular, Google Play shows a "Storage is full, please remove any of these apps:" message, however, I have about 20GB left from my storage. I googled this plenty, and came up with this solution: https://forum.xda-developers.com/general/general/how-to-fix-insufficient-storage-t2855191, which says that I have to give access to the system user to the app-lib folder in order for things to install. However, when I check the permissions on this folder (and its subfolders) I can see that the permissions for them are already granted to the system, as can be seen here:
Besides that, I have cleared caches, wiped data storage and system, and reinstalled Magisk many many times since, but none of these have helped with this issue. Something to note here is that if I uninstall Magisk, I can download apps again. It is only when Magisk is installed that the system is unable to access the storage.
Please if someone has any idea on how to fix this I'd be the most thankful!
Click to expand...
Click to collapse
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.

XiaomiFixer69 said:
I had the same problem 2 years ago. What I did was buy another phone (an iPhone). It didn't fix the problem, but a friend of mine was very happy. Strongly recommended.
Click to expand...
Click to collapse
Stupid solution [emoji1787]
Enviado do meu ASUS_I001DC através do Tapatalk

Cannot Root my redmi note 8 ginkgo

Hello
I have a redmi note 8 when I was on MIUI 12.0.1 magisk was working perfectly with zygisk and all the modules I had.
After updating to MIUI 12.5 I lost it and that update was so laggy and full of issue so I went back to MIUI 12.0.1.
When I flash the magisk 24.3 after changing it to a zip file it flash with TWRP with no issue but when I turn on the phone I find the magisk icon when I clicked on it it asked to download and install magisk but it never does it keep the message downloading even the app had access to the storage, so I cancel that and Install the magisk APK :
{
"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"
}
which ask that it requires addtional setup and I click OK but it said it fails
then the phone become so laggy when I check the internal storage I find that the phone created a folder named 0 and start copying all file and folder from the internal storage to that folder.
When I try to unistall it from the application it said that it hasn't acess to \data
so I went to TWRP and removed it with a uninstaller zip, if I insall and old version of magisk like 23 I dont get this kind of issue
any help please.

1. you have accidentially duplicated your internal storage /sdcard aka /storage/emulated/0 aka /data/media/0.
connect adb shell in TWRP recovery. I assume you are firm with basic toybox coreutils cp, rm etc. you have to do it manually from command line in TWRP adb shell or terminal because you lost root (requires TWRP, OrangeFox, RedWolf or whatever custom recovery with encryption support or unencrypted device).
- merge /data/media/0/0 into /data/media/0 and
- delete unwanted /data/media/0/0 duplicate directory to free up disk space
Don't make any mistakes, you might lose your pictures, WhatsApp media, etc. from Internal Storage.
2. clean Magisk installation
- delete /data/adb directory and
- wipe /cache partition
- install Magisk again
You will lose all modules and superuser settings.

aIecxs said:
1. you have accidentially duplicated your internal storage /sdcard aka /storage/emulated/0 aka /data/media/0.
connect adb shell in TWRP recovery. I assume you are firm with basic toybox coreutils cp, rm etc. you have to do it manually from command line in TWRP adb shell or terminal because you lost root (requires TWRP, OrangeFox, RedWolf or whatever custom recovery with encryption support or unencrypted device).
- merge /data/media/0/0 into /data/media/0 and
- delete unwanted /data/media/0/0 duplicate directory to free up disk space
Don't make any mistakes, you might lose your pictures, WhatsApp media, etc. from Internal Storage.
2. clean Magisk installation
- delete /data/adb directory and
- wipe /cache partition
- install Magisk again
You will lose all modules and superuser settings.
Click to expand...
Click to collapse
Thanks for the answer I tried all the above things except removing /data/adb and wipe cache partition
I installed magisk 23.0 yesterday but didnt accept to do the requires addtional setup.
should I remove magisk then try to install the latest one then do step 2?
another question I must not reboot the phone after clean Magisk installation in step 2 just feolow the other steps directly ?

I did what you asked and it worked
the only issue I had is I couldn't install the magisk 24.x so I installed the 23.0 and updated and everything is good
thanks

(ROM)(A5)(Stock)(8.0) N'CreamOSv2 (Tweaked, Deodexed, Busybox, DeKnoxed, Decrypted and Rooted)

{
"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"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Many others features coming from stock Oreo ROM
Busybox added to xbin
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W) the one which i have tested (works fine)
Maybe F, K, L and S variants (Tell me if it works please)
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- N'CreamOS_8.0_v2_a5y17lte
Thanks to
AndroDef------ For his helpfull Classy Kitchen XDA Link
Topjohnwu------ For his irreplacable Magisk Root Magisk Github
sfirmware.com------ For the stock TAR.MD5 file SM-A520W(XAC)
If you see some bugs, please inform me

its just like samsung experience, i relly like it )

It is working fine on my Galaxy A520F Exynos Model, so you can check that out from the compat. checklist. For some reason the os thinks this is a A520W, but this is a F Model. I had a problem where TWRP said that flashing failed with error 7, but then I restarted it and I flashed it and it worked. Also you actually don't need a SD Card for the flasheble zip, you can actually just turn MTP on and Mount the DATA partition and copy the zip from your computer to your phone. This ROM is pretty good!

Oops, wrong post.