Hi,
Is there anyway to still use Android Pay with a bootloader unlocked and rooted 3T?
It should work if you use a kernel with Sultanxda's patch (such as franco.Kernel) and phh's SuperUser with Magisk and Magisk Hide enabled.
I'm still able to use Android Pay on OOS with stock kernel. I rooted with Magisk + Phh's SuperUser and enabled Magisk Hide for Android Pay.
jbw716 said:
I'm still able to use Android Pay on OOS with stock kernel. I rooted with Magisk + Phh's SuperUser and enabled Magisk Hide for Android Pay.
Click to expand...
Click to collapse
Are you messing me with bro? I just got mine 2 days ago, do not want to lose Android Pay - need to know for sure 100%!!!
I am currently running OxygenOs 3.5.4 (latest OTA update), what about you ?
After hours of investigating I am 90% confident it will work - but still want to remove remaining 10% of the doubt.
eurosickwitit said:
Are you messing me with bro? I just got mine 2 days ago, do not want to lose Android Pay - need to know for sure 100%!!!
I am currently running OxygenOs 3.5.4 (latest OTA update), what about you ?
After hours of investigating I am 90% confident it will work - but still want to remove remaining 10% of the doubt.
Click to expand...
Click to collapse
Why would I lie?:angel:
I'm on 3.5.4 and it's working flawlessly! If it doesn't work for you, all you'd have to do is unroot though. No big deal.
jbw716 said:
Why would I lie?:angel:
I'm on 3.5.4 and it's working flawlessly! If it doesn't work for you, all you'd have to do is unroot though. No big deal.
Click to expand...
Click to collapse
Pumped, was going to wait until tomorrow but screw that - can't wait and live without Xposed after years of being hooked right ? haha. As you said at worst i will unroot.:cyclops:
eurosickwitit said:
Pumped, was going to wait until tomorrow but screw that - can't wait and live without Xposed after years of being hooked right ? haha. As you said at worst i will unroot.:cyclops:
Click to expand...
Click to collapse
Oh. It works with Phh's SuperUser with Magisk, but you can't use Xposed. Sorry!
I found this XDA page saying otherwise dated August 2016. It also links me to Official Magisk thread.
Page: https://www.xda-developers.com/use-android-pay-with-xposed-without-rebooting-with-magisk/
Magisk thread: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In Magisk thread it states that "Bind mount and load nearly any existing mod that modifies system, includes popular mods like root and Xposed" which sounds to me like all is good. Were you maybe just not aware of it? I hope Xposed part also true, have to read the thread further and see.
Hey all,
I'm running into the same issue. I have OOS 4.0.2 with unlocked bootloader, have tried custom kernel (blu_spark), with phh's SuperUser and Magisk. Problem is, I can't find the Android Pay app in Magisk Hide, and the kernel doesn't seem to be working to mask the unlocked bootloader from SystemNet either. Any help?
knw257 said:
Hey all,
I'm running into the same issue. I have OOS 4.0.2 with unlocked bootloader, have tried custom kernel (blu_spark), with phh's SuperUser and Magisk. Problem is, I can't find the Android Pay app in Magisk Hide, and the kernel doesn't seem to be working to mask the unlocked bootloader from SystemNet either. Any help?
Click to expand...
Click to collapse
Why use a custom kernel? I'm using stock and it works fine. Instructions:
Reflash 4.0.2 in recovery (you won't lose data)
Flash Magisk 10.2 ONLY
Reboot and install phh superuser and Magisk Manager from the play store
Open phh superuser and fiddle with the settings so root is kicked in
Open MM and test SafetyNet (should be fine)
Then use Magisk Hide (enable in settings) for Android Pay
So, turns out I managed to get it to work. I removed Magisk and PHH apps, reflashed stock boot.img, and then the blu_spark kernel. After that, Android Pay worked without a problem.
If I need root for some reason later, I'll try Magisk/phh again, but that has me settled for now.
Anyone has got succesfully SafetyNet with OOS4.0.3? I have Magisk v11.1 and pph Superuser but still does not work.
tyler19820201 said:
Anyone has got succesfully SafetyNet with OOS4.0.3? I have Magisk v11.1 and pph Superuser but still does not work.
Click to expand...
Click to collapse
Magisk now includes its own root solution, so you shouldn't use phh's Superuser with it anymore,
tyler19820201 said:
Anyone has got succesfully SafetyNet with OOS4.0.3? I have Magisk v11.1 and pph Superuser but still does not work.
Click to expand...
Click to collapse
UPDATE
I have solved the issue. I am using multiROM and have realized ONLY the Internal ROM getting the safetynet pass!! So i was swap my internal OOS4.0.2 ROM (before was 4.0.3 but i was downgrading ) with the Lineage OS. And now the Lineage is the internalROM and the oxygen is the secondary. The Lineage getting safetynet pass but the oxygen does not. Before swapping Oxygen having pass but Lineage does not...
Hope will help this who want to set it up in the future.
Are you saying I can root Oxygen OS 4.0.3 (or whatever 4 version), install Magisk and root with it somehow, enable MagiskHide for AndroidPay , AND have Xposed as well? Currently I have all these capabilities on 3.5.3 with all of the above, and I'm able to successfully use Android pay (important for my lifestyle).
Is this already possible with OOS 4 and Magisk?
If not root with phh superuser (like I had to on Marshmallow OOS 3) and not SuperSu, then how do you root with Magisk? Mind little link?
Please tell me if Android Pay works with Magisk alongside of Xposed. So hesitant to move although I made all backups just don't wanna and have hours to trial and error right now. Any help or more info to specific question above much appreciated.
I'm ready for it, got TWRP installed (might need to update it), did full backup, also app Titanium backup like a good boy. Just waiting for real confirmation from people using AndroidPay would be nice for me personally.
eurosickwitit said:
Are you saying I can root Oxygen OS 4.0.3 (or whatever 4 version), install Magisk and root with it somehow, enable MagiskHide for AndroidPay , AND have Xposed as well? Currently I have all these capabilities on 3.5.3 with all of the above, and I'm able to successfully use Android pay (important for my lifestyle).
Is this already possible with OOS 4 and Magisk?
If not root with phh superuser (like I had to on Marshmallow OOS 3) and not SuperSu, then how do you root with Magisk? Mind little link?
Please tell me if Android Pay works with Magisk alongside of Xposed. So hesitant to move although I made all backups just don't wanna and have hours to trial and error right now. Any help or more info to specific question above much appreciated.
I'm ready for it, got TWRP installed (might need to update it), did full backup, also app Titanium backup like a good boy. Just waiting for real confirmation from people using AndroidPay would be nice for me personally.
Click to expand...
Click to collapse
Everything in your first paragraph is possible except Xposed (which doesn't exist for Nougat yet). The latest version of Magisk automatically gives you root when you install it with no extra steps, as long as you don't already have SuperSU.
Works fine on Latest FreedomOS
This works great on Freedom OS which is based off Oxygen 4.0.3. I was able to add my card to Android Pay without any issues yesterday. I rooted by just flashing the Magisk 11.1 zip as it install Magisk SU during the process. No other SuperSU or phh SuperSU is needed. Just the Magisk 11.1 zip, and enable Magisk Hide with magisk manager. All is working great
Can I do this with Oxygen 4.0.3 Stock without flashing a custom kernel? I would just like to install Magisk and keep the stock kernel if possible.
GeorgeOSbeta said:
Can I do this with Oxygen 4.0.3 Stock without flashing a custom kernel? I would just like to install Magisk and keep the stock kernel if possible.
Click to expand...
Click to collapse
It's possible it won't harm you. Magisk has an uninstall zip that will remove everything. Don't forget to enable Magisk Hide
Sent from my ONEPLUS A3000 using Tapatalk
{
"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"
}
Working great
Sent from my ONEPLUS A3000 using Tapatalk
Related
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
Magisk v12.0 - Root & Universal Systemless Interface To ZF2 (Z00A-Z008) adrian1234a
{
"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"
}
Magisk can ROOT your device, along with standard common patches.
It packs with a super powerful Universal Systemless Interface, allowing unlimited potential!
Magisk modifies boot image and add files to /data and /cache
It touches your /system partition only if root installed in /system is detected!
Features
100% fully open source and easy to build!
Magic Mount:
Allow you to do any system (vendor) modification without actually tampering the partitions.
MagiskSU: Open Source Root Solution
Root your device with MagiskSU, based on phh's Superuser, which is based on CM Superuser.
Magisk Manager:
MagiskSU Root Management, Install / Upgrade Magisk in-app,
Manage, Upgrade, Download, Install Magisk Modules within a few taps.
Magisk Hide:
Hide Magisk from detection, including SafetyNet, which is used in Android Pay, Pokemon GO etc.
Resetprop:
Allow you to do any modifications to system props (build.prop), including read-only props.
Multiple Entry Points:
Provide several entry points to developers, reliably pausing the boot process before everything is done.
Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
Standard Stuffs:
Remove dm-verity, forceencrypt; includes a super complete busybox to guarantee consistent behaviour, and can also be toggled to be used universally.
You are not forced to a single root solution for Magic Mount and other features
However, only two choices are provided: systemless SuperSU and MagiskSU
It will attempt to remove any other root, and install MagiskSU by default
Any Question: Discord server
And if you like my work donate my
This FIX Work On All Roms but borets kernel is not compatible
adrian1234a said:
This FIX Work On All Roms
Click to expand...
Click to collapse
And on new borets kernel/rom? Thanks for your work!
samuele94 said:
And on new borets kernel/rom? Thanks for your work!
Click to expand...
Click to collapse
this rom is not compatible with any magisk is problem by kernel sorry
adrian1234a said:
this rom is not compatible with any magisk is problem by kernel sorry
Click to expand...
Click to collapse
If i have Borets ROM, but i switch kernel to Zenkernel ??? Do you think it works ???
adrian1234a said:
this rom is not compatible with any magisk is problem by kernel sorry
Click to expand...
Click to collapse
Thanks!!!
fgbustoa said:
If i have Borets ROM, but i switch kernel to Zenkernel ??? Do you think it works ???
Click to expand...
Click to collapse
Yes, it's only kernel problem
Sent from my ASUS_Z00AD using XDA Labs
I have cleanstock rom ? Its okie for that rom ?
fgbustoa said:
If i have Borets ROM, but i switch kernel to Zenkernel ??? Do you think it works ???
Click to expand...
Click to collapse
Yeah
ishantanish said:
I have cleanstock rom ? Its okie for that rom ?
Click to expand...
Click to collapse
What is your kernel
Im pretty new to Magisk world... someone can give a simple procedure to correctly install Magisk ???
ROM: Borets
KERNEL: ZenKernel
ROOT: Systemless SuperSU 2.79
Thanks
fgbustoa said:
Im pretty new to Magisk world... someone can give a simple procedure to correctly install Magisk ???
ROM: Borets
KERNEL: ZenKernel
ROOT: Systemless SuperSU 2.79
Thanks
Click to expand...
Click to collapse
Download the last version
Wipe two caches
Install
Reboot
Enjoy!!!!
fgbustoa said:
Im pretty new to Magisk world... someone can give a simple procedure to correctly install Magisk ???
ROM: Borets
KERNEL: ZenKernel
ROOT: Systemless SuperSU 2.79
Thanks
Click to expand...
Click to collapse
or uninstall supersu
And the other is same
Is there a tutorial on signing the original file? Would like to see how it works
adobrakic said:
Is there a tutorial on building this from source?
Click to expand...
Click to collapse
No i add the asus_sign and i edit the update-script
Fix Update To magisk 11.6!!!!
I have borets kernel and this fix works there
Flashed borets kernel after flashing fix and magisk was showing all red and root didn't work
But flashed fix again and it's working
V11.6 with borets
@persieghini
What OP mean is it isn't compatible with Borets ROM due to the kernel that already patched with Systemless SuperSU.
Sent from my Redmi 3 using XDA Labs
adobrakic said:
Is there a tutorial on signing the original file? Would like to see how it works
Click to expand...
Click to collapse
Just compare the 2 zip files, adrian added this to the META-INF\com\google\android\update-binary script:
Code:
ui_print "- Inserting Zenfone 2 Sign by adrian1234a"
cat $INSTALLER/common/zf2_6_sig >> new-boot.img
mv new-boot.img $NEWBOOT
And he added the sig file in common.
Thank you for this thread adrian!
Android P NotoColorEmoji Replacerget 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
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?
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This build includes microG, a free and open implementation of the Google Play Services Framework. It allows applications calling proprietary Google APIs to run on AOSP-based ROMs like Replicant and LineageOS. Acting as a replacement for the closed-source Google Apps (GAPPS), it is a powerful tool to reclaim your privacy while enjoying Android core features such as Google Cloud Messaging.
It also includes WireGuard, a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.
I probably won't do other types of builds unless somebody has a really terrific suggestion. These builds exists for my own convenience and I thought I'd share it with the XDA community where I've been lurking and leeching for years.
Features
Embedded root (can be enabled in Developer Settings)
Restricted (system-only) signature spoofing
microG (FakeStore, GmsCore, GsfProxy, legacy mapsv1 implementation)
Mozilla Location Services + Nominatim for network-based location
FDroid (+Privileged Extension)
WireGuard-enabled LineageOS kernel
Monthly automagical OTA updates (signed builds, https)
Reporting Bugs
I just build using the latest official LineageOS (also see this thread), wireguard patch, TheMuppets proprietary files and microG prebuilts. Report any "regular" bugs to those threads and/or Git pages unless you're sure the problem is unique to these builds.
Initial installation
NOTE: TWRP gets replaced by the stock recovery every time you install a ROM zip. Either use fastboot to boot TWRP or flash the TWRP zip file every time after you flash a ROM zip.
OnePlus firmware must be installed on your device on both A/B slots. Hence the instructions below tell you to flash OxygenOS twice.
Wipe system, data and cache.
Flash latest OxygenOS using TWRP.
Reboot to TWRP
Flash OxygenOS again using TWRP.
Reboot to TWRP
Flash the newest build using TWRP.
Reboot to TWRP.
Flash the newest build using TWRP again.
Reboot and enjoy!
OTA Updates
For OTA updates, use the built-in Updater app. Everything should JustWork(TM) without any TWRP/recovery magic.
Downloads
https://lineage.darwinkel.net/builds/full
Delta/partial updates are not supported.
I recommend Aurora Store if you want to download and install apps from Google Play.
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Cygnust said:
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Click to expand...
Click to collapse
This build has a free software alternative to opengapps baked-in. This ROM is probably not what you're looking for if you want to install the regular Google Play Services. No clue about Magisk or a custom kernel surviving OTA.
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Tomatot- said:
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Click to expand...
Click to collapse
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
AndroidBolder said:
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
Click to expand...
Click to collapse
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Master One said:
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Click to expand...
Click to collapse
I'm not that fond of Magisk and neither are the LineageOS devs. I don't use any apps that use SafetyNet and this works for me personally (I mainly use root for Yalp Store and WireGuard). I have, however, tested it. I enabled DroidGuard and microG's SafetyNet attestation and tested it with an app. Unfortunately, it didn't seem to pass even with root disabled in developer settings. Magisk Hide might help, though.
Toni Moon said:
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
Click to expand...
Click to collapse
I'm pretty sure you can install a Google Play Store APK, but you would have to disable or remove FakeStore for it to work, I think. I personally use Yalp Store to download apps from Google Play (including paid ones).
EDIT: download speeds have been fixed.
1 Question, how to get snapchat and chromecast work?
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I don't use either of those apps, no clue.
Can I use blue Spark twrp?
noky76 said:
Can I use blue Spark twrp?
Click to expand...
Click to collapse
You can.
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Master One said:
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
Click to expand...
Click to collapse
Sounds really interesting, but the way you're putting it, it seems somewhat unstable/unreliable. VoLTE works fine with my carrier so I have no way to test it. If multiple people can confirm it works without causing instability then I'll consider changing build.prop.
Master One said:
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
Click to expand...
Click to collapse
I presume addonsu remove would work, no clue if the 15.1 version works on Pie. Did a quick search but I can't find one for LOS16. Bingo! uploaded by Luk1337, one of the LOS devs.
admiralderp said:
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Click to expand...
Click to collapse
Like most custom roms slightly worse than OxygenOS, but completely fine otherwise!
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
nksonfire said:
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
Click to expand...
Click to collapse
It works on most custom ROMs as long as you use Maps 9.82.1
Thank you a TON for providing these builds. This finally gives me a path to move off of OxygenOS. Installed, tested, everything working beautifully *including VoLTE and VoWiFi* (on U.S. T-Mobile).
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I have managed a way to get at the very least Snapchat working on this ROM.
Flash as normal.
After that, flash Magisk from TWRP.
Add the *Nanodroid*, not official, microG repo to F-Droid and install the DroidGuard Helper from there. You'll have to web-search "nanodroid fdroid repo" as I cannot provide external links on this new account.
(I've not tested any of this with the official repo's DroidGuard Helper, but there are issues on microG's Github repo suggesting that SafetyNet will only pass with Nanodroid's version of DroidGuard Helper.)
Install a file manager with root capability (such as Amaze on F-Droid) and navigate to /data/app where you will find the DroidGuard Helper under "org.microg.gms.droidguard-randomstringhere". Move this folder to /system/priv-app and reboot.
Make sure SafetyNet is on in microG Settings and ensure it is using the official server (by hitting the three dots in the corner, selecting Advanced and selecting "Use official server".)
Enable Magisk Hide in Magisk Manager and enable hiding for Snapchat and DroidGuard Helper.
Try SafetyNet attestation under Magisk Manager. Hopefully both checks should pass.
Enjoy.
I did a test OTA (the current 1/30/19 version is available there, so I just downloaded and installed it again) and the only changes to be made were to re-flash TWRP and Magisk then re-install DroidGuard Helper and move it to /system/priv-app. All microG and Magisk Manager settings were retained.
As your post says, I have a really terrificant suggestion.
Why don't you try to port Sailfish Os on op6?
If you think that my suggestion is not terrificant I will understand. I would like to port it but I can't do that. For many reasons. Bye and congrats for this build. it looks like great.
Ceers