Database Develop

[2019.5.1][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27)

Prerequisite
Magisk is required to be installed on your device!​Magisk - The Universal Systemless Interface​
Support Devices
All Magisk compatible devices
Downloads
My Xposed zip is universal across all architectures and Android versions.
https://androidfilehost.com/?fid=1395089523397956629
Install Guide
Install the XposedInstaller in the attachments
Follow the instructions in the Magisk release thread to install Magisk on to your device
Install Xposed within Magisk Manager's Download Section, or download the zip and flash in custom recovery
For uninstallation, remove the Xposed Magisk Module within Magisk Manager
Systemless Xposed does not pass SafetyNet!!!
Credits
@rovo89 for creating Xposed
Source
All binaries are downloaded and repacked from either places:
Official build from rovo89
I did not recompile/change anything how Xposed works, the behavior should be 100% identical to original sources, if you experience any Xposed issues, please directly report to the original threads.

Changelog
v87.0
- Include fix from rovo89 to prevent bootloops in the latest security patch
- Android 5.1 (SDK 22) was broken after one Magisk upgrade, it's now Magisk version independent
v86.6 (Downloaded 126324 times)
- Update to support the new repo system of Magisk
- Fixed incompatibility of suhide
v86.5 (Downloaded 174328 times)
- Update for the new API of Magisk v4
- NOTE: In order to update to Magisk v4, you are required to uninstall Magisk completely before upgrading. Please look at the main Magisk thread for more info
v86.4 (Downloaded 16246 times)
- Revert the disable to not mount method for Android Pay
- Fixed alt version script typo
v86.3
- Use Magisk as dependancy
- Support all the way back to Android 5.0
- Android Pay
v86.2 (Downloaded 30608 times)
- Script updates, more info here
v86.1 (Downloaded 10185 times)
- Minor fixes, release notes here
v86.0
- Massive update, see release notes here
v85.7 (Downloaded 15774 times)
- Hot fix for some devices which breaks proper init commands
v85.6
- Add SELinux label when executing script, should fix the few devices that aren't working
- Massively improve the script to handle /cache to /data migration (the rare case when /data isn't available in TWRP)
- Add Pixel C support (not-tested)
- Combine all architecture into an All-In-One flash zip, users will only need to be aware of their own Android version
v85.5
- Combine image mount and bind mount into one single script, should be more reliable and cleaner, hopefully it will fix ALL previous issues
- Add more logs to boot for debugging
- Add SDK 22 support (un-tested!!)
v85.4
- The mounting method should now support all devices
- The installer will now merge Xposed Image if possible, so feel free to place your own files under /xposed
v85.3
- Improved compatibility for some recoveries with incorrect libraries
- Changed the method to mount xposed.img, hopefully will fix issues on some devices
v85.2
- Separate Systemless Xposed from SuperSU. It now uses it's own image in data (/data/xposed.img)
- Won't effect SuperSU anymore. Both are now working independently
- Massively updated flash script, should be more reliable (e.g. Prefer sukernel in su.img over bundled binary)
- (Derived from Wanam's update) Add Huawei theming engine support (details); Ensure the recompilation on Huawei EMUI Roms (details).
v85.1
- Fixed flash script not installing files issue
v85.0
- Initial release

Wow! I will test it as soon as possible!
If you agree I can merge your changes in my build and add these zip files in the available zip files list to download

Updated the OP for more information

Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!

5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
Oh really?!
This is cool, it seems that the Safety net check is not that strict lol

Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(

koko115 said:
Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(
Click to expand...
Click to collapse
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.

topjohnwu said:
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk

koko115 said:
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk
Click to expand...
Click to collapse
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks

5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.

topjohnwu said:
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.
Click to expand...
Click to collapse
Hmm. How did you test? I used to get blocked by SafetyNet when I tried to add a card. Today, after deactivating Xposed and rebooting, I was able to add a card, but I haven't tried to make a purchase yet.
I'll switch to systemless Xposed the next time I update my ROM. Hopefully it will become the default install method. @rovo89 mentioned the possibility of going systemless a while ago but said he didn't plan to work on it.

topjohnwu said:
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks
Click to expand...
Click to collapse
{
"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'm still not sure from reading the op or any posts whether ap works with this. Anything conclusive?

i Found one bug
i founded one bug, is in update-binary, doesnt extract xposed.prop ,xposedbridge.jar and libxposed_art.so.

In /su i dont see any xposed files
---------- Post added 30-05-2016 at 12:04 AM ---------- Previous post was 29-05-2016 at 11:40 PM ----------
I manually put missing this 3 files to /su and works great. THX

Thank you @koko115
OP updated with a version that should be working.
I forgot to put spaces in the previous release

The x86 version has a few downloads now.
Is the x86 working as expected? Can anyone report if it works?

I'm getting hung up on this step: "Flash systemless Xposed"
Would that be to say reboot into TWRP, press Install and pick the arm64 for my HTC 10?
Thanks!!
UPDATE: That's exactly what I did, worried I bricked my phone there for a second the boot logo took very long but now it's optimizing all the apps and starting up.
UPDATE 2: Success!!

Works great! Only the app says xposed 85.0 is installed but it's actually 85.1. Probably something you didn't edit because twrp also thought it was 85.0 [emoji2]
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app

Xposed installed and active, but not working.

I recently updated my OP2 to OOS 3.0.2, and I installed xposed on it like i normally would. Everything installed without problems, but none of my modules are working. Can someone help me?
I have checked that I have the correct xposed for marshmallow. I have checked that I have the newest apk, any other suggestions?

By any chance, do you have Xposed Status disabled?
{
"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"
}
Sent from my Nexus 6P using Tapatalk

If it still doesn't work, you can try to uninstall Xposed Installer > reboot your phone > install Xposed Installer and than do a soft reboot (by function on Xposed Installer app ).
This work for me. I think the problems happen because I flash xposed *.zip file after install Xposed Installer
Goodluck.

Curiousn00b said:
By any chance, do you have Xposed Status disabled?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
What apk is that? When I said latest I ment 3.0 Alpha 4. The apk you use doesnt look one bit like that.
Mark2014 said:
If it still doesn't work, you can try to uninstall Xposed Installer > reboot your phone > install Xposed Installer and than do a soft reboot (by function on Xposed Installer app ).
This work for me. I think the problems happen because I flash xposed *.zip file after install Xposed Installer
Goodluck.
Click to expand...
Click to collapse
Did not change anything, sadly

lauge2000 said:
What apk is that? When I said latest I ment 3.0 Alpha 4. The apk you use doesnt look one bit like that.
Click to expand...
Click to collapse
Material Design Xposed Installer.
Did not change anything, sadly
Click to expand...
Click to collapse
Could you either upload screenshots from your Xposed Installer framework section or upload your Xposed log file? It would be easier to help you without only guessing around based on few information.
You could also try to uninstall your framework by flashing the uninstaller.zip within recovery and flash the systemless Xposed afterwards.

Portgas D. Ace said:
Material Design Xposed Installer.
Could you either upload screenshots from your Xposed Installer framework section or upload your Xposed log file? It would be easier to help you without only guessing around based on few information.
You could also try to uninstall your framework by flashing the uninstaller.zip within recovery and flash the systemless Xposed afterwards.
Click to expand...
Click to collapse
Here is a picture of my Xposed installer section.
https://i.imgur.com/tcqZNH3.png
Here is my Xposed log file: https://www.dropbox.com/s/zibe3nywkxzyqzc/xposed_error_20160615_100528.log?dl=0

lauge2000 said:
Here is a picture of my Xposed installer section.
https://i.imgur.com/tcqZNH3.png
Here is my Xposed log file: https://www.dropbox.com/s/zibe3nywkxzyqzc/xposed_error_20160615_100528.log?dl=0
Click to expand...
Click to collapse
Any specific reason why you are using v83 instead of the latest version?

Also disable all of your modules
Enable one of them; imho, start with snapprefs because it looks, from your log that it is working.
Reboot, open snapchat if it works disable snapprefs and enable another module reboot and check if that module's functions work.
Continue doing this until done.
One of your modules is bad, I am 75% sure it is custom alert slider from nqk. The last comments in its thread seem to point to it not working in Android6.0.1.
http://forum.xda-developers.com/oneplus-2/themes-apps/app-alert-slider-oneplus-2-t3248005/page13

Portgas D. Ace said:
Any specific reason why you are using v83 instead of the latest version?
Click to expand...
Click to collapse
Tried v85 and it didnt work, just thought I would try v83 instead
Nergal di Cuthah said:
Also disable all of your modules
Enable one of them; imho, start with snapprefs because it looks, from your log that it is working.
Reboot, open snapchat if it works disable snapprefs and enable another module reboot and check if that module's functions work.
Continue doing this until done.
One of your modules is bad, I am 75% sure it is custom alert slider from nqk. The last comments in its thread seem to point to it not working in Android6.0.1.
http://forum.xda-developers.com/oneplus-2/themes-apps/app-alert-slider-oneplus-2-t3248005/page13
Click to expand...
Click to collapse
Will try this, thanks!
EDIT: I have now tried this, and it didn't work. Anything else I can try?

Can no one help with this??

lauge2000 said:
Can no one help with this??
Click to expand...
Click to collapse
Having the same problem, tried everything with no luck...

Hi.
We had the same issues on the Elephone P9000, also on the UMI Super.
I've made a MOD (grorkmod http://forum.xda-developers.com/showthread.php?p=67247504 ) that will create a patched sepolicy (thanks again to @Chainfire for his sukernel and supolicy) which will be copied into root on every boot.
On boot the stocksepolicy will stay initially, but in the later bootprocess it will be overwritten with a patched one.
The problem in detail:
We have only stockbased ROMs with an enforcing kernel. If we set selinuxmode to permissive with an initd script lots of apps won't work. EBay, google messenger, runtastics and more will just crash. Xposed modules will work but not the apps.
With the grorkmod you have both and that on an enforcing ROM.
It should work on other devices also, but it has to be tested.
Maybe it could solve your problems, too?
For other devices than the elephone p9000 it is strongly recommend to use the latest v0.94.
Greetings
Vsrookie
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
Hi.
We had the same issues on the Elephone P9000, also on the UMI Super.
...[/URL]
Click to expand...
Click to collapse
I have set SElinux to permissive with terminal, but modules still don`t work.

gaich said:
I have set SElinux to permissive with terminal, but modules still don`t work.
Click to expand...
Click to collapse
You have to boot in permissive mode. Create a script in init.d with setenforce 0.
greetings
vsrookie
ps: On our chinese phones that was a problem, thats why i created grorkmod.
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
You have to boot in permissive mode. Create a script in init.d with setenforce 0.
greetings
vsrookie
ps: On our chinese phones that was a problem, thats why i created grorkmod.
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Great!!!! This did the trick! I flashed your mod and my modules began to work!:laugh:

Hi.
Nice to hear. May i ask you what phone you have?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
Hi.
Nice to hear. May i ask you what phone you have?
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, it`s in my signature - Ulefone Vienna with Marshmallow test build.

i have the same problem and ended up just uninstall xposed and installer.

[Magisk Module][Flashable Zip][5.0+] Android P NotoColorEmoji Replacer v5

Android P NotoColorEmoji Replacer​​get Android P's emojis on any Android device running Android 5.0+!​
Hi all,
This is my first Magisk module, and with a very simple purpose: Getting the newest Android P emojis working in your device running Android 5.0+ with Magisk (as a possibility to install them systemlessly), or replacing the actual font using the included Flashable Zip.
How did it look?
Old Emojis:
Android O's Public Beta 1 Emojis:
Prerequisites
Magisk v11.6 or higher, in case of using the Android O Magisk Module.
Magisk v15.0 or higher, in case of using the Android P Magisk Module.
A working custom recovery (TWRP, PhilZ, etc.)
Tested on
Both module and flashable Zip had been tested on AOSP 7.1.1, AICP 7.1.2 and RR_N, working perfectly in the three scenarios. However, except for the 'racial' emojis, they should work in any Android 5.0+ device.
If you own a device which is running Android between 5.0 and 6.0.1, please kindly let me know if the module works as expected
Downloads
Magisk Module - from the attachments, in the future in the Magisk Manager repository (once topjohnwu adds it!), and from my server.
Flashable Zip for System A partitions - from the attachments, and from my server.
Flashable Zip for System A/B partitions - from the attachments, and from my server.
Differences between Magisk Module and Flashable Zip versions
Magisk Module - Requires Magisk installed, and will work systemlessly, without modifying the system partition of your device (recommended!)
Flashable Zip - Replaces the system font inside your device, so making a backup of it before is highly recommended.
Installation instructions
Magisk Module (via Magisk Manager) - Download it from the attachments or from my server. Open the Magisk Manager app, go to the Modules section and hit the + button. Choose the downloaded Zip and install it. Once done, reboot your device as suggested by Magisk Manager.
Magisk Module (via Custom Recovery) - Download it from the attachments or from my server. Reboot your device into recovery mode, then choose Install, locate the downloaded Zip and flash it.
Flashable Zip - Download the version depending on your device's needs, either from the attachments or from my server. Reboot your device into recovery mode, then choose Install, locate the downloaded Zip and flash it.
Troubleshooting
I've seen some people that wiped their /data partition (aka Wipe Data/Factory reset), and thus losing their magisk.img and all their modules, since they're stored there.
This means: If you factory reset your device and didn't flash Magisk flashable Zip again, none of the modules will be able to work.
To fix it, flash Magisk flashable zip again, then flash all your modules, and it should all be working again.
Apart from this I've also seen that Substratum themes custom fonts override the system fonts, so maybe there's another reason why it sticks to the old font. If that's the case, try removing them and see if the new emojis display or not.
Much love <3

Cant install it, there's an error when I flash using TWRP wich says 'Status Error 7: Tu madre'
What can I do?
Enviado desde mi Xperia M2 Aqua mediante Tapatalk

iFlashed said:
Cant install it, there's an error when I flash using TWRP wich says 'Error 7: Tu madre'
What can I do?
Enviado desde mi Xperia M2 Aqua mediante Tapatalk
Click to expand...
Click to collapse
Hi Daniel, nice to see you here too
Have you tried doing "sudo rm -rf /" already?
NOTE in case it wasn't clear enough: This is obviously a banter...

linuxct said:
Hi Daniel, nice to see you here too
Have you tried doing "sudo rm -rf /" already?
NOTE in case it wasn't clear enough: This is obviously a banter...
Click to expand...
Click to collapse
Nice! Working now thanks for your contribution!
Enviado desde mi Xperia M2 Aqua mediante Tapatalk

Nice for those interested, hope you'll do a Magisk emoji replacer to have Android Nougat Emoji's on Android O Final release. I don't really like the new one, it seems, to me, that we're going back to the old emojis from the skeuomorphic Apple Era.

Bokoblin said:
Nice for those interested, hope you'll do a Magisk emoji replacer to have Android Nougat Emoji's on Android O Final release. I don't really like the new one, it seems, to me, that we're going back to the old emojis from the skeuomorphic Apple Era.
Click to expand...
Click to collapse
Firsts things first, let's hope that the (already-in-the-works) Magisk v13.0 is fully compatible with Android O final release, or if it isn't, that topjohnwu doesn't need much effort to get it working . And once that happens, try to get the old-school emojis back with it.
However, I have to note the following: In Android O, there's a new feature called EmojiCompat, which is a library that allows emojis to be downloadable per-app needs. This means that, if a developer includes the library, it will try to download the newest possible emoji fonts directly from Google and apply them inside the app.
Here's an example in Allo.
{
"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"
}
Those [x] symbols in the right screenshot, using the EmojiCompat library, would convert into a taco and a unicorn again just like the sender sees them, no matter what version of Android you're running (starting from Android 4.4+).
Providing this, it's possible that, if apps start to implement it, you'd see the newest emojis although you systemlessly replaced them by the old-school ones...
Have this link as reference: https://developer.android.com/preview/features/emoji-compat.html

linuxct said:
Firsts things first, let's hope that the (already-in-the-works) Magisk v13.0 is fully compatible with Android O final release, or if it isn't, that topjohnwu doesn't need much effort to get it working . And once that happens, try to get the old-school emojis back with it.
However, I have to note the following: In Android O, there's a new feature called EmojiCompat, which is a library that allows emojis to be downloadable per-app needs. This means that, if a developer includes the library, it will try to download the newest possible emoji fonts directly from Google and apply them inside the app.
Here's an example in Allo.
Those [x] symbols in the right screenshot, using the EmojiCompat library, would convert into a taco and a unicorn again just like the sender sees them, no matter what version of Android you're running (starting from Android 4.4+).
Providing this, it's possible that, if apps start to implement it, you'd see the newest emojis although you systemlessly replaced them by the old-school ones...
Have this link as reference: https://developer.android.com/preview/features/emoji-compat.html
Click to expand...
Click to collapse
Yey, finally they did something about it haha, that's awesome. Thanks for the module btw (I personally don't like stock Google emojis tho xD)

Awesome. Good work on the module. Keep it up.

Great Emojis thanks for this running LineageOS 13.0 Sprout device.

Working on LG G5 with Android 7.0
Thanks for the good work.
Working without issues on LG G5 with Android 7.0

Applied it but the emoji haven't changed. I clear the data of the keyboard. Does it work with swiftkey app?
Sent from my Moto X Play using Tapatalk

I Will test on s8+ now

K.khiladi said:
Applied it but the emoji haven't changed. I clear the data of the keyboard. Does it work with swiftkey app?
Sent from my Moto X Play using Tapatalk
Click to expand...
Click to collapse
I'm not sure if Swiftkey bundles their own emoji set, and I've only tried on Google Keyboard. Try downloading Google's Keyboard (AOSP Keyboard is also valid), and see if they changed there or not.
However, although it doesn't necessarily need to be related to this case, I've seen some people that wiped their /data partition (aka Wipe Data/Factory reset), and thus losing their magisk.img and all their modules, since they're stored there.
This means: If you factory reset your device and didn't flash Magisk flashable Zip again, none of the modules will be able to work.
To fix it, flash Magisk flashable zip again, then flash all your modules, and it should all be working again.

works great on my lineageOS 14.1 kenzo

Just installed it on my Nexus 6P running dirty unicorns 11.3.
Sent from my Nexus 6P using XDA Labs

Flashed via TWRP. All good ? Xperia ZR stock.

Thanks for sharing.
Just tested the zip and flashed true twrp and cleared cache but not working for me in latest dirty unicorn on my oneplus 3.
Did try twice and with google aosp keyboard and swift keyboard but no luck with both off them.
Regards ysco..

Does the phone has to be rooted in order for this to work?

ysco said:
Thanks for sharing.
Just tested the zip and flashed true twrp and cleared cache but not working for me in latest dirty unicorn on my oneplus 3.
Did try twice and with google aosp keyboard and swift keyboard but no luck with both off them.
Regards ysco..
Click to expand...
Click to collapse
Can you please try the following?
linuxct said:
However [...], I've seen some people that wiped their /data partition (aka Wipe Data/Factory reset), and thus losing their magisk.img and all their modules, since they're stored there.
This means: If you factory reset your device and didn't flash Magisk flashable Zip again, none of the modules will be able to work.
To fix it, flash Magisk flashable zip again, then flash all your modules, and it should all be working again.
Click to expand...
Click to collapse
Mania626 said:
Does the phone has to be rooted in order for this to work?
Click to expand...
Click to collapse
Root =/= having a working recovery. It's specified in the OP that all you need is a working Custom Recovery like TWRP (and magisk if you're doing it systemlessly) in order to get it working.

Mania626 said:
Does the phone has to be rooted in order for this to work?
Click to expand...
Click to collapse
Yes

[MODULE][Test-C01] ★ Alienoid-OS ★ | Custom Overlay ROM

{
"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"
}
Intro:
This is an overlay rom for many devices featured by AlienoidMod.
NOTE!!! All thing are prototypes now and in very experimental condition.​
Feature Updates:
Apps
ViPERFX | Modified Viper4Android
Lawnchair | Customizable Pixel Launcher
Phonograph | Music Player
Binaries
7za, adb, busybox, fastboot, sqlite3, zipalign
and AlienoidMod Framework script (amf).
AlienoidMod Framework script
For now it's in a very under-developing condition but the future concept is (amf) will be the hive mind of whole overlay system. It will understand the current android rom conditions where it will be installed then it will define the tasks... I'll write more later...
Downloads:
Follow the attachments...
Contributors
metaspook
Version Information
Status: Test
Test Version: C01
Release Date: 2017-09-17

Reserved

Reserved

metaspook said:
★
★​
AlienoidMod
This is a framework where many apps, mods, binaries for cross-devices, multi-arch, different roms with versions are belongs to.
Alienoid-OS
This is an overlay rom for many devices featured by AlienoidMod
NOTE!!! All thing are prototypes now and in very experimental condition.​
Test-A logs: <<< Regular check this for updates
App: ViPERFX (modified Viper4Android for AlienoidMod )
Bin: 7za, adb, fastboot, sqlite3
and a HiveMind written by me.
Downloads:
Follow the attachments...
Click to expand...
Click to collapse
Hello,
I don't understand what your magisk module does make after installed.
You mean: "Bin: 7za, adb, fastboot, sqlite3", it contain all theses binaries and an ViperFX modded apk too ?

Yea I'm interested as to what the binaries and other mods besides viper are for. If I use this I'd just take viper out anyway, I use ARISE instead.
Sent from my LG Nexus 5X using XDA Labs

Dont know about the other bin files.
Finally! Your Viper is now 4.5.0.5 driver.. asks for install driver... It should install on flashing... Maybe
The new interface is much better!
All working fine! ?

L.F.B. said:
Dont know about the other bin files.
Finally! Your Viper is now 4.5.0.5 driver.. asks for install driver... It should install on flashing... Maybe
The new interface is much better!
All working fine! ?
Click to expand...
Click to collapse
Wait 4.5.0.5? Don't you mean 2.5.0.5?
Sent from my LG Nexus 5X using XDA Labs

Rom said:
Hello,
I don't understand what your magisk module does make after installed.
You mean: "Bin: 7za, adb, fastboot, sqlite3", it contain all theses binaries and an ViperFX modded apk too ?
Click to expand...
Click to collapse
Yes...
Its an overlay ROM so u can use it over many lollipop+ roms
adb and fastboot are for arm, arm64 archs now...

metaspook said:
Yes...
Its an overlay ROM so u can use it over many lollipop+ roms
adb and fastboot are for arm, arm64 archs now.
Click to expand...
Click to collapse
What do the mods do though exactly? Any explanations?
Sent from my LG Nexus 5X using XDA Labs

metaspook said:
Yes...
Its an overlay ROM so u can use it over many lollipop+ roms
adb and fastboot are for arm, arm64 archs now.
Click to expand...
Click to collapse
Ok, so many framework in one package, right ?

Galaxy S6 7.0 magisk 13

kapiszon53 said:
Galaxy S6 7.0 magisk 13
Click to expand...
Click to collapse
What's screenshot is this? This is not the ViPERFX app from Alienoid-OS !!

Rom said:
Ok, so many framework in one package, right ?
Click to expand...
Click to collapse
not framework but kind of that It Alienoid-OS will utilize the AlienoidMod framework.

Sorry, wrong screenshot
So, I flashed your zip without errors but ViperFX was not installed after boot. So I installed ViperFX manually from your zip and that's what happend:

metaspook said:
not framework but kind of that It Alienoid-OS will utilize the AlienoidMod framework.
Click to expand...
Click to collapse
Is there a link for information on AlienoidMod I can look at?
Sent from my LG Nexus 5X using XDA Labs
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
kapiszon53 said:
Sorry, wrong screenshot
So, I flashed your zip without errors but ViperFX was not installed after boot. So I installed ViperFX manually from your zip and that's what happend:
Click to expand...
Click to collapse
Yea you can't install viper manually unless its the original one. It needs to patch the necessary lines in your audio_effects.conf to register the driver.
Sent from my LG Nexus 5X using XDA Labs

Skittles9823 said:
Is there a link for information on AlienoidMod I can look at?
Sent from my LG Nexus 5X using XDA Labs
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
Yea you can't install viper manually unless its the original one. It needs to patch the necessary lines in your audio_effects.conf to register the driver.
Sent from my LG Nexus 5X using XDA Labs
Click to expand...
Click to collapse
So i'm a bit cunfused. All I want is ViperFX running on magisk 13 as it did on magisk 12. Is this mod for me?

Skittles9823 said:
Is there a link for information on AlienoidMod I can look at?
Click to expand...
Click to collapse
Not yet cuz I didn't open thread for it and as u can see I wrote everything is very experimental now even this thread would also temporary may be, for now this thread is for test builds testing so whenever I upload the new test builds please install it and let me know what have u experienced, explored like about the apps, mod, bins etc working or not and how about it etc...
All of your feedback could help me build this thing better and make a matured form..

kapiszon53 said:
So i'm a bit cunfused. All I want is ViperFX running on magisk 13 as it did on magisk 12. Is this mod for me?
Click to expand...
Click to collapse
Yes there are other modules which are just ViperFX in this magisk forum. Given I haven't used them since I prefer to have the modules from ARISE over just viper any day of the week.
Sent from my LG Nexus 5X using XDA Labs

kapiszon53 said:
So i'm a bit cunfused. All I want is ViperFX running on magisk 13 as it did on magisk 12. Is this mod for me?
Click to expand...
Click to collapse
Did you flashed using Magisk 13.3???

metaspook said:
Not yet cuz I didn't open thread for it and as u can see I wrote everything is very experimental now even this thread would also temporary may be, for now this thread is for test builds testing so whenever I upload the new test builds please install it and let me know what have u experienced, explored like about the apps, mod, bins etc working or not and how about it etc...
All of your feedback could help me build this thing better and make a matured form..
Click to expand...
Click to collapse
Alright I'll give it a flash and see what I come up with. I'm not exactly sure I have use for bins and stuff though. I am curious as to what hive mind is though.
Sent from my LG Nexus 5X using XDA Labs

Is there a Systemless XPosed for the Exynos Note 8?

Hey guys,
Trying to install the systemless XPosed for Nougat on my Note 8, but for some reason, after installation, it stops my 256GB Exynos Note 8 from booting up. Was able to recover it by running the Magisk uninstaller via TWRP.
Noticed that on the official XPosed thread, it states that it'll 'cause boot loop issues on stock Samsung ROM, but on the Systemless XPosed Page, it claims the SDK 24 and 25 are universal, so, what's wrong?
Any suggestions on getting systemless XPosed working on my Exynos Note 8 with Nougat? I especially want the systemless variant as it allows easy on/off whenever I'm going shopping and want to use Android Pay instead of having to uninstall all modules.

Bump

I have mine working perfect on v.88 on my n950n 256gb here are some pics.
{
"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"
}
Sent from my SM-N950F using Tapatalk

tokoam said:
I have mine working perfect on v.88 on my n950n 256gb here are some pics.View attachment 4299111View attachment 4299112
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
You seem to have v87.3 installed, which is an earlier version and I can't find that in Magisk's manager app. Mind shearing the zip file of that v87.3?
If you install v88, I think the same boot loop will occur on your device....

MrElectrifyer said:
You seem to have v87.3 installed, which is an earlier version and I can't find that in Magisk's manager app. Mind shearing the zip file of that v87.3?
If you install v88, I think the same boot loop will occur on your device....
Click to expand...
Click to collapse
Are you blind ?
Sent from my SM-N950F using Tapatalk

tokoam said:
Are you blind ?View attachment 4299174
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Well your first image image clearly states v87.3 so I could ask you the same.
https://forum.xda-developers.com/attachment.php?attachmentid=4299195&stc=1&d=1507703428
Either way, for some odd reason, installing XPosed via the Magisk manager stops mine from booting up, even on a clean installation. Did you install it via the Magisk manager or from where did you install it?

MrElectrifyer said:
Well your first image image clearly states v87.3 so I could ask you the same.
https://forum.xda-developers.com/attachment.php?attachmentid=4299195&stc=1&d=1507703428
Either way, for some odd reason, installing XPosed via the Magisk manager stops mine from booting up, even on a clean installation. Did you install it via the Magisk manager or from where did you install it?
Click to expand...
Click to collapse
That does not mean that's the version that's installed ! The second picture I circled Clearly illustrates that so you are wrong .The v.87 that your pointing to is a link to that version available for download. It does not indicate that framework is installed ! They just have not updated that yet. If you click on get support on XDA thread link it will bring you to topjohnwu thread where you could download the updated frameworks [emoji30]
Sent from my SM-N950F using Tapatalk

What is the main advantage of systemless Xposed? safety-net still works? I tired Magisk v14 and default Xposed on my Sammy tab s2 with android N and all worked ok, no boot loops. Just do a backup and try flashing Xposed the worst thing you get will be bootloop or soft brick

Magisk is nice cause it does not allow apps to inject code as the frameworks does not bind to the os.Makes it safer and may run better in some cases
Sent from my SM-N950F using Tapatalk

Ok, so I've tried all of the following in attempts to install the systemless XPosed, all to no avail:
- Via the Magisk manager
- Via TWRP recovery using the systemless XPosed zip files
On the contrary, when I install XPosed v88.1 from within the custom XPosed Installer app provided in this systemless XPosed OP, my Note 8 does boot up, but it's not the systemless XPosed I'm looking for.
Maybe I'm using a non-compatible ROM? My Build number is NMF26X.N950NKSU1AQI2, Android Security Patch Level August 1st, 2017. I did download the latest available firmware from Samsung using the SamFirm v0.3.6 tool, and it downloaded a SM-N950N_1_20170904150113_hn123cimwz_fac.zip file, then I used the Odin 3 v3.12.7 tool to install the largest tar.md5 file in the zip package as there were 6 for some reason in the package. I'm new to using a Samsung Smartphone, this Note 8 is my first ever from them. Is this the same build number on your 256GB Exynos Note 8 @tokoam?

Same here, always was getting bootloops when installing systemless (with official and cooked rims). This was the case with unofficial systemless 87.3 and now with official systemless 88.x .
Normal xposed was was/is working. But normal xposed 88.x is causing high cpu, heating and instabilities! I see others complaining in the xposed thread.

yes but it will fk your note 8 up
i flashed it then ended up deleting it as soon after due to the phone being super slow and weird vibration

renegade said:
Same here, always was getting bootloops when installing systemless (with official and cooked rims). This was the case with unofficial systemless 87.3 and now with official systemless 88.x .
Normal xposed was was/is working. But normal xposed 88.x is causing high cpu, heating and instabilities! I see others complaining in the xposed thread.
Click to expand...
Click to collapse
Damn, that sucks. Do you have the same build number as I pointed out above? You also using the 256 GB Exynos Note 8?Wonder how it's working for @tokoam and not on our devices.

MrElectrifyer said:
Damn, that sucks. Do you have the same build number as I pointed out above? You also using the 256 GB Exynos Note 8?Wonder how it's working for @tokoam and not on our devices.
Click to expand...
Click to collapse
Nope. I have the Exynos 64 MB version!

Any other suggestions for getting this fixed?

It was causing heating issues I removed it all together. I'll wait for a stable release
Sent from my SM-N950F using Tapatalk

tokoam said:
I have mine working perfect on v.88 on my n950n 256gb here are some pics.View attachment 4299111View attachment 4299112
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
hi where did you buy it becuse i had note 8 and there was no oem unlock
Sent from my iPhone using Tapatalk

tokoam said:
It was causing heating issues I removed it all together. I'll wait for a stable release
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Right, looks like I'll just stick with the non-systemless version for now and keep checking to see if there's a working systemless variant.
azq8ooz said:
hi where did you buy it becuse i had note 8 and there was no oem unlock
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Please don't hijack my thread, search the forum and create a new thread if necessary.

azq8ooz said:
hi where did you buy it becuse i had note 8 and there was no oem unlock
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ebay
Sent from my SM-N950F using Tapatalk

anyone have luck installing systemless xposed? i keep getting stuck in bootloop...
if i was to install the non systemless xposed will this fail the safety net?