Related
Hello.
After many many reinstall of magisk I still cant find "Enable Busybox" in Magisk settings
I have "magisk core only mod" , "Magisk Hide" and "Systemless Host" BUT "Enable Busybox" is missing/not visible in my settings of Magisk.
I also got error when Safety Net check. Only bacisintegry is successfull. ctsProfile do not pass the test.
But, I can still download and update payed and free apps from Google Play Store.
Anyone what to do for getting "Enable Busybox" to be visible in my Magisk settings?
And, since ctsProfile not pass safetyscheck..can that be because for that missing "Enable Busybox" in settings?
Running lineageOS 14.1 and samsung J5 ( 2016 ) , SM-J510FN
Magisk 14.0
Regards
Rolf
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Didgeridoohan said:
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
[email protected] said:
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
Click to expand...
Click to collapse
SafetyNet Fixed by doing this:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
BUT, still Netflix Error/not compatibel vs my device when download from Google Play. Got a message in that error message downloading Netflik from Netflix's site. Doing that..and Netflix up running
Thanks again Didgeridoohan for pointing me in the right direction
Regards
Rolf
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
SlimPickens89 said:
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
Click to expand...
Click to collapse
There is a busybox integrated into Magisk, for use by Magisk...
If you wan't busybox for the rest of your system, install the busybox module from the Magisk repo.
Didgeridoohan;73790549There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: [url said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417[/url]
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Peter.1997 said:
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Click to expand...
Click to collapse
If you only need busybox for Viper4Android, try the awesome ViPER4Android FX module (available in the Magisk repo). It doesn't need busybox...
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Peter.1997 said:
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Click to expand...
Click to collapse
Judging from your two posts, I'd say something's wrong with your Magisk installation... Magisk log and magisk_debug.log (from /data) might show something interesting.
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Sebastl said:
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Click to expand...
Click to collapse
Sounds like your TWRP isn't up to the job... It's probably too old (info which would have been in the log ) or otherwise missing some features...
Updating TWRP or letting the Manager patch a boot image that you then flash manually are two possible solutions.
Thank you very much for the quick reply Didgeridoohan.
That is of course water on the mills of the "always include logs" - people. Apparently for a reason
TWRP Version is/was 3.02.
After you suggested patching the image from Magisk Manager, i tried that and got a quick and dirty "Failed".
But i realized that now the option "Direct Install (recommended)" was available.
It wasnt when i did the initial setup.
As i had nothing to loose, i tried that to reinstall and after the next reboot -
Bingo! Now the busybox binary is/was available and therefore the Busybox Module and consequently also Xposed respective everything which depends on unzipping/busybox works.
Strange - but somehow problem solved.
I didnt see anything in the TWRP changelogs from 3.02 up to 3.2.1 - but hey...
Hope that helps someone.
Greetings and a nice 2018 !
PetNoire's SafetyNet Spoofer
This module tries to pass SafetyNet on devices/roms that don't.
This started when i put LineageOS on my phone and couldn't play Pokemon GO anymore. much sadness was had.
i searched around for a fix and found universal-safetynet-fix. Awesome! it let me play pokemon again but it broke everything else root related while it was enabled.
So, i worked on updating it to be compatible with magisk 17. and i got it! (download at the bottom)
but, well.. there was a lot in that code that didn't need to be there anymore. (does anyone even use magisk 12?!)
and worse still, my phones stock image used a thumbprint, not a fingerprint. with it in usnf, it didnt even pass basic integrity!
so i got to work and PetNoire's SafetyNet Spoofer was born!
Disclaimer:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
I also do not support hacking/altering any other apps with your root powers.
i made this purely to legitimately play a game on a customized system.
Information
Features:
Resets system props to a factory state
spoofs the device fingerprint or thumbprint
has a friendly command tool to change finger/thumbprint settings
Use:
Flash it with TWRP or MM.
by default, it spoofs the same device that unsf did which is enough for most uses. Congrats, you're done!
you can also use the pnss command as root to change, reset, or disable the fingerprint spoofing.
run the 'pnss' command from terminal for usage information
example command:
Code:
su
pnss set thumb MyDeviceThumbprint/8.1/etc/etc
Requeriments
Magisk v17
Installation
Flash the .ZIP from TWRP or MM Module page
Reboot
Known issues
thumbprint mode is only passing BasicIntegrity, not CTS
Donations
If you feel I helped you, you can buy me a coffee here
Credits
@Deic - the original creator of universal-safetynet-fix here
@PetNoire - porting it to magisk 17, breaking it further, and adding thumbprint support
Download
Please DO NOT share the module itself or the download link, share the thread only.
vv
@PetNoire May I ask a favour (as I've done to other users that hav updated @Deic's module to the current template in the past)? If you're going to re-release the module with the current template, at least please fix it so that it no longer replaces Magisk's internal Busybox with it's own. Really bad practice and we never did get @Deic to fix that before he disappeared...
If you need a specific module Busybox, place it in the module folder instead and call the commands from there, or make sure that the users know that they have to install @osm0sis Busybox, or if you're really in a pinch just use the internal Magisk Busybox then, but at least don't replace it with one that have the possibility to mess up Magisk's internal functions.
Also, it would be a good idea if you gave @Deic a bit more credit than you're doing right now (a tiny, tiny link at the top of your post just isn't enough), no matter that he's MIA. All you've really done is to transfer his module to the current template and added a check for the current Magisk version and it's paths. I'd suggest you make that more apparent so you don't risk being accused of passing someone else's work off as your own.
Didgeridoohan said:
@PetNoire May I ask a favour (as I've done to other users that hav updated @Deic's module to the current template in the past)? If you're going to re-release the module with the current template, at least please fix it so that it no longer replaces Magisk's internal Busybox with it's own. Really bad practice and we never did get @Deic to fix that before he disappeared...
If you need a specific module Busybox, place it in the module folder instead and call the commands from there, or make sure that the users know that they have to install @osm0sis Busybox, or if you're really in a pinch just use the internal Magisk Busybox then, but at least don't replace it with one that have the possibility to mess up Magisk's internal functions.
Also, it would be a good idea if you gave @Deic a bit more credit than you're doing right now (a tiny, tiny link at the top of your post just isn't enough), no matter that he's MIA. All you've really done is to transfer his module to the current template and added a check for the current Magisk version and it's paths. I'd suggest you make that more apparent so you don't risk being accused of passing someone else's work off as your own.
Click to expand...
Click to collapse
Thanks for the tip on busybox. I thought it was pretty weird that it replaced it like that for 2 commands but was more concerned about getting it to work at all. I'll look into fixing that soon.
update: i think i almost have it working on magisk's busybox but still working out some bugs.
And I'll edit it to give him some more credit right away.
PetNoire said:
Thanks for the tip on busybox. I thought it was pretty weird that it replaced it like that for 2 commands but was more concerned about getting it to work at all. I'll look into fixing that soon.
Click to expand...
Click to collapse
That would be great.
I thought I'd give some insight into what the module actually does, for those that are wondering, since it might get lost in translation between the different updates to the module by others than @Deic.
The USNF module is made up of two parts. For one, it changes the device fingerprint to a certified one to pass the ctsProfile check (the in-built one is a Xiaomi print, but IIRC you can also use the device stock fingerprint if it's already certified). This is also something that can be done with a Magisk boot script (post-fs-data.d or service.d) and the resetprop tool:
Code:
resetprop ro.build.fingerprint <certified fingerprint value>
There are also Magisk modules available that do the same thing (apart from USNF).
Device Spoofing Tool by @Dreamer(3MF) is one (although it also changes a whole lot of other props to simulate a OnePlus 2).
And there's also my MagiskHide Props Config that changes the build fingerprint to one of your choice.
Or, if you don't care about the systemlessness, you can directly edit your build.prop file and change the current ro.build.fingerprint to a certified one.
So, for the device fingerprint and passing the ctsProfile there are a few options.
The second part of USNF is the custom MagiskHide (as described in the OP). The thing here though, is that for the majority of devices it is not necessary anymore, since (as it also says in the OP) @topjohnwu have fixed most of those issues. From what it seems, from user reports in different threads, this is only necessary on some MIUI releases (Xiaomi devices). The module actually started out as a "Xiaomi SafetyNet fix" (check the module id), but the build fingerprint part turned out to be useful for other devices, so @Deic changed the name to "Universal". All other devices should be good with only changing the device fingerprint.
So far, it doesn't seem like the custom MagiskHide from the module is interfering in any way with the real thing. But, considering that it hasn't been updated in over a year, who knows.
Class dismissed.
Is there any reason to keep the code for old magisk? Does anyone still use 12-14?
Seems to have helped on my S8 with KingROM
My Magisk updated to 17.1 and then GooglePay started getting upset that I had rooted, mucked around with various things including the 'MagiskHide Props Config' module which my S8 never seems happy with (random reboots when installed) but this seems to do the trick.
I installed via Magisk Manager but it seemed to kill the Magisk install when I rebooted, reinstalled Magisk and now all seems ok so a big thumbs up from me
I wonder how the magiskhide part (at least the "add", etc. scripts) can work, because you use the old outdated "/magisk"-folder, that is no longer supported since 16.3 (or so).
Oberth said:
My Magisk updated to 17.1 and then GooglePay started getting upset that I had rooted, mucked around with various things including the 'MagiskHide Props Config' module which my S8 never seems happy with (random reboots when installed) but this seems to do the trick.
I installed via Magisk Manager but it seemed to kill the Magisk install when I rebooted, reinstalled Magisk and now all seems ok so a big thumbs up from me
Click to expand...
Click to collapse
For some reason it doesn't always work the first time. Usually just rebooting fixes it.
jenslody said:
I wonder how the magiskhide part (at least the "add", etc. scripts) can work, because you use the old outdated "/magisk"-folder, that is no longer supported since 16.3 (or so).
Click to expand...
Click to collapse
I thought I changed it all. You sure there isnt some kind of version check? I'll look at it later
Again first goal was to get it working. Next goal is to make it awesome
Hmm.. this doesn't work with my phone (HTC one M8). After I flashed it, wiped cache (TWRP), it said "complete" on the log, then it will never boot to my OS, stuck on the HTC logo, no boot animation. I use TWRP
winzzzzz said:
Hmm.. this doesn't work with my phone (HTC one M8). After I flashed it, wiped cache (TWRP), it said "complete" on the log, then it will never boot to my OS, stuck on the HTC logo, no boot animation. I use TWRP
Click to expand...
Click to collapse
In-Case Of Facing A Bootloop/Bootscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery.
winzzzzz said:
Hmm.. this doesn't work with my phone (HTC one M8). After I flashed it, wiped cache (TWRP), it said "complete" on the log, then it will never boot to my OS, stuck on the HTC logo, no boot animation. I use TWRP
Click to expand...
Click to collapse
Does it boot after disabling the module?
From twrp>advanced>terminal:
HTML:
Mount -o loop /data/adb/magisk.img /mnt
Touch /mnt/universal-safetynet-fix/disable
The reboot
so.. i kind of deleted the whole magiskhide clone from the module and just left the prop configs and its totally passing safetynet now. so i guess the normal magiskhide is enough and is just missing some prop resets.
@PetNoire I still failed to pass safetynet, When I flashed the module, my magisk was erased, but then I just saw from this thread that a reboot is needed. After reboot my magisk came back, but It' says "Requires Additional Setup" I ignore it and then checked if safetynet will pass, It failed.
I'm using stock CM FLARE S4 ROM android 5.1.
Sorry for my English.
Thankyou for the reviving this module. :good:
Godbless you.
PetNoire said:
so.. i kind of deleted the whole magiskhide clone from the module and just left the prop configs and its totally passing safetynet now. so i guess the normal magiskhide is enough and is just missing some prop resets.
Click to expand...
Click to collapse
That was kind of the point of my longish text above... All you need to pass on a device that doesn't fully pass SafetyNet (ctsProfile fails while basicIntegrity passes), is usually just to change ro.build.fingerprint to a certified fingerprint (and there are several ways to go about that, but the Magisk way always involves the resetprop tool somehow). Custom ROMs, developer versions of OEM firmwares (Oneplus 6 beta, for example), and otherwise uncertified devices can usually pass SafetyNet like this.
Didgeridoohan said:
That was kind of the point of my longish text above... All you need to pass on a device that doesn't fully pass SafetyNet (ctsProfile fails while basicIntegrity passes), is usually just to change ro.build.fingerprint to a certified fingerprint (and there are several ways to go about that, but the Magisk way always involves the resetprop tool somehow). Custom ROMs, developer versions of OEM firmwares (Oneplus 6 beta, for example), and otherwise uncertified devices can usually pass SafetyNet like this.
Click to expand...
Click to collapse
This was just the first one that gave me any success so I initially assumed it was because of the hiding. I wasn't even able to pass basic integrity without this one and most others didn't help either. I tries yours at one point with no success. Do you change all the "dangerous props" that this one does?
PetNoire said:
This was just the first one that gave me any success so I initially assumed it was because of the hiding. I wasn't even able to pass basic integrity without this one and most others didn't help either
Click to expand...
Click to collapse
Basic integrity passing has nothing to do with the device fingerprint or other props. With Magisk, that usually means that MagiskHide isn't working (for whatever reason, most of the times it just needs a restart) or you have something installed that MagiskHide can't hide (like Xposed, remnants of other kinds of root, etc).
Edit: Scroll down a little here for a table of examples of what will cause a true or false cts profile or basic integrity response.
https://developer.android.com/training/safetynet/attestation#compat-check-response
iamcurseal said:
@PetNoire I still failed to pass safetynet, When I flashed the module, my magisk was erased, but then I just saw from this thread that a reboot is needed. After reboot my magisk came back, but It' says "Requires Additional Setup" I ignore it and then checked if safetynet will pass, It failed.
I'm using stock CM FLARE S4 ROM android 5.1.
Sorry for my English.
Thankyou for the reviving this module. :good:
Godbless you.
Click to expand...
Click to collapse
I don't know what Tue additional setup does, but I always do it and its been working. Also your device may have thumbprint props instead of fingerprint.
Run this in a terminal and let me know what you get
Code:
getprop | grep print
PetNoire said:
I tries yours at one point with no success. Do you change all the "dangerous props" that this one does?
Click to expand...
Click to collapse
My module changes all the common fingerprint props, but as far as I know, it's only ro.build.fingerprint that is important for the ctsProfile check.
Didgeridoohan said:
Basic integrity passing has nothing to do with the device fingerprint or other props. With Magisk, that usually means that MagiskHide isn't working (for whatever reason, most of the times it just needs a restart) or you have something installed that MagiskHide can't hide (like Xposed, remnants of other kinds of root, etc).
Edit: Scroll down a little here for a table of examples of what will cause a true or false cts profile or basic integrity response.
https://developer.android.com/training/safetynet/attestation#compat-check-response
Click to expand...
Click to collapse
I wiped all partitions, installed lineage 15, installed magisk and enabled hide and it wouldn't pass basic at any point. Even still its never passed it without this module. It didn't even pass it on the clean install, before magisk
Hey all, I use SELinuxModeChanger apk to set Permissive mode when my device (Xperia Z5Compact) starts.
I would like to use a Magisk module to do it instead. What is the best module (simple, light on resources) to do so?
I just need the device to start in Permissive mode and that's pretty much it.
I notice all the modules that do this were removed from Magisk repo.. why is that, stability issues?
Thanks.
Because it just takes a very simple boot script, something that a Magisk module is a bit of overkill for. To keep the Magisk repo somewhat uncluttered (it's still quite messy), the decision was made to remove all modules that were just too simple.
Why do you want to change to a Magisk module? It'll do the exact same thing as your app... If you really want to skip the app, just put the following inside a file (you can name it whatever, say "selinux", doesn't even need an extension), place it in /data/adb/service.d, give it execution permission and that's it:
Code:
#!/system/bin/sh
setenforce 0
That'll change to permissive at each boot. You could do the same with an app like Tasker, etc...
Very helpful if I need to do it manually, thank you very much!
I just found this module : https://forum.xda-developers.com/apps/magisk/selinux-mode-inverter-t3775271
which I think will do the trick nicely (I like to be able to enable or disable the feature easily from within Magisk).
Didgeridoohan said:
Because it just takes a very simple boot script, something that a Magisk module is a bit of overkill for. To keep the Magisk repo somewhat uncluttered (it's still quite messy), the decision was made to remove all modules that were just too simple.
Why do you want to change to a Magisk module? It'll do the exact same thing as your app... If you really want to skip the app, just put the following inside a file (you can name it whatever, say "selinux", doesn't even need an extension), place it in /data/adb/service.d, give it execution permission and that's it:
That'll change to permissive at each boot. You could do the same with an app like Tasker, etc...
Click to expand...
Click to collapse
Nice idea, I'm using it and loving it, thanks for the info.
Thanks for the ROM. Its very stable and smooth. But i faced with one issue after last update
Any gcam is crashing except for the stock(6.2) on Pixel Experience ROM (last update10.0)I tried different cases like clean cache, removed Google photo, install other gcam mods, change SElinux. Nothing helped me. Has anyone encountered anything like this? Any solution?
Developers: LSPosed Developers
Homepage: GitHub
✱ Requirements:
• Magisk 21+
• Android 8.1-13
• Riru(NOT NEEDED) USE ZYGISK
Description: Riru module providing ART interception framework (natively for Android Pie) that provides consistent API -interfaces with OG Xposed, using YAHFA (or SandHook) interception environment, supports Android 8.1 ~ 11.
& Installation:
• Install Riru 23+
• Install Riru - LSPosed via Magisk Manager
• Install LSPosed Manager app (Note: No Saparate App and Zip, App Will be Installed Automatically)
• Reboot your device.
Download:
For stable release, please go to Github Release page For canary build use telegram.
Go to second post for latest version Download
Notes:I'm just sharing this from github, I'm not responsible if you bricked your device.
GPay and other banking apps working fine without any issue so this xposed alternative is worth trying and safer.
Note: If anyone facing bootloop issue, don't panic, hard reboot again and it will work.
Screenshot:
Download:
Flash zip file through magisk and then install LSPosed Manager app
Update 1 March 2021
V1.2.0
V1.3.7 Updated 15.May.2021
(Note: No Saparate App and Zip, App Will be Installed Automatically)
For Newer Version Changelogs and Downloads:
LsPosed Github
Changelog
Spoiler: See
Fix manager white screen
[*]Support split-apk modules (LSPosed will choose only one apk with xposed_init to load)
[*]Fix manager crash when launching an uninstalled module from notification
[*]Load modules with SharedMemory (it can speedup app cold launch) 2
[*]New manager icon
[*]Fix incorrect update notification in the first installation
[*]Fix some apps not showing in the scope list in some rare cases
[*]Show notification of module uninstallation
[*]Prevent modules from hooking inner methods (methods from XposedBridge's classloader)
Note:
Previously LSPosed only recognize modules from the primary user. However, this strategy is not good and leads to some problems: some modules require getting installed app lists for configuration but they cannot do so across users; some require reading themselves from the hooked apps but they cannot do so from non-primary users; some users want to configure modules differently on different users which is not feasible previously. Thus LSPosed now requires every module to be installed to the user on which the apps they want to hook are installed. Some devices restrict modules from installing onto some users. In such a case, you can install them from the manager (but it's recommended).
1: For some weird devices that prevent installing apps from the root user, please install the manager from /data/adb/lspd/manager.apk or manager.apk from the zip file manually.
2: Some modules get modules' apk path using reflection of its classloader, it's not recommended and unstable since the apk path from classloader no longer exists when using SharedMemory to load modules. Please use the documented way (from IXposedHookZygoteInit.StartupParam.modulePath) instead.
Reserved 2
Why it's safer than EdXposed?
QkiZMR said:
Why it's safer than EdXposed?
Click to expand...
Click to collapse
I didn't say it's safer than edxposed. I meant xposed alternatives like taichi etc.
All banking apps works, no system slowdown, i got more free ram etc.
In edxposed the hooked apps take time to open, no such issue with LSPosed.
That's why i thought it's worth trying and safer.
And +1 is safetynet passes all the time with LSPosed but, with edxposed safetynet works for some time after every reboot even with blacklisting google framework and services.
This slowdown is caused by YAHFA hook in EdXposed. On Sandhook is much better. Which hook method you use in LSposed?
And +1 is safetynet passes all the time with LSPosed but, with edxposed safetynet works for some time after every reboot even with blacklisting google framework and services
Click to expand...
Click to collapse
SafetyNet works till google patched it no matter which xposed clone you use. Before last patch SN was working fine with EdXposed. I don't needed blacklisting framework and services because EdXposed manager is doing automatically, with special option enabled. So don't say lies about EdXposed but tell us about technical differences between LSposed and EdXposed. What you change after forking EdXposed repo?
looks working good u,till now, just its annoying sometimes to have to choos which app has the module applies. a "select all" option would be welcome in a next release
How do I pass safety net? I have universal safety fix module is installed too.
Antho02 said:
looks working good u,till now, just its annoying sometimes to have to choos which app has the module applies. a "select all" option would be welcome in a next release
Click to expand...
Click to collapse
This is what i was confused about? ive never chosen before. I dont know which ones i need things like HiddenCoreModule to apply to? Everything?
It looks like this xposed clone works only in whitelist mode...
I'm quite amazed that this edxposed alternative is running much better than edxposed itself on my android 11, aosp rom, redmi k30 pro zoom. Really glad that I came across this!
Thanks for the great and awesome work devs!
Preparedtobereckless said:
This is what i was confused about? ive never chosen before. I dont know which ones i need things like HiddenCoreModule to apply to? Everything?
Click to expand...
Click to collapse
Apply to System Framework.
Hidden core module do nothing, try no device check module. BTW safetynet passes for me by default.
darashikoh said:
How do I pass safety net? I have universal safety fix module is installed too.
Click to expand...
Click to collapse
What are LSposed module we can use in A11
Im trying to ask the scope list of my modules. Firefds minminguard hiddencore and hide mock location. Anybody can help for the whitelist ??
what does mean: "select other app for each module" ?
for example for "GravitiyBox" module, which app should be enable and why?!
mrhamed said:
what does mean: "select other app for each module" ?
for example for "GravitiyBox" module, which app should be enable and why?!
Click to expand...
Click to collapse
Android System - android
Call - com.samsung.android.incallui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.r.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
It also depends on what firmware you are using amd what features you've enabled in gravity box. Enable these according.
What I've enabled in miui are shown in image below.
a module based selection, what to hook seems a good approach of doing what you want and at the same time saving resources. a more advanced selectiin UI would be good. filter based on words and then select in the filtered list, select deselect all. in addition I have no idea what some modules are hooking like gravity box...this is just an example...I know I can find out however maybe the manager app can support to find out or tick what is recommended
I am trying LSposed on my OnePlus 7 Pro (GM-1917), OOS 10.3.8, Magisk 21.4, xXx 12.4.
I followed these instructions from the OP ...
• Install Riru 23+
• Install Riru - LSPosed via Magisk Manager
• Install LSPosed Manager app
• Reboot your device.
Click to expand...
Click to collapse
I got into what seems to be an infinite boot loop. I waited 3-5 minutes, but the boot loop continued.
Has anyone seen this behavior? If so, is there a workaround?
Thank you in advance.
UPDATE: I must have messed up one or more of the installation steps the first time around. I retried installing, and now LSPosed works for me with no boot loop.
OnePlus 7 Pro (GM-1917)
OOS 10.3.8
Magisk 21.4
Magisk Manager 8.0.7
xXx 12.4
Riru 23.4
LSPosed-v0.5.4.0-5135-release.zip (YAHFA)
LSPosedManager-v0.5.4.0-5175-release-signed.apk
Good work!
Onward!
HippoMan said:
I am trying LSposed on my OnePlus 7 Pro (GM-1917), OOS 10.3.8, Magisk 21.4, xXx 12.4.
I followed these instructions from the OP ...
I got into what seems to be an infinite boot loop. I waited 3-5 minutes, but the boot loop continued.
Has anyone seen this behavior? If so, is there a workaround?
Thank you in advance.
Click to expand...
Click to collapse
Working fine with OnePlus 7t latest beta. There might be some other issue. LSPosed doesn't seem to cause bootloop. Share logcat.
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
Thanks a lot. I have been searching for a while since I moved to use Zygisk and finally found this post.
However, do you know if there is any reliable detector about init.rc hiding? I've been using MagiskDetector. While it correctly showed that init.rc was not modified after installing your module, after a day or two it would suddenly report modified init.rc. I've read posts saying MagiskDetector is not accurate as it sometimes reports this even if magisk is not installed. I just want to make sure init.rc has been correctly hidden. Thanks.
You're welcome. My module just runs the same code as riru-momohider for hiding init.rc modficiations. The sudden detection you mention may be a false positive of MagiskDetector. Since I installed the module (under Magisk Zygisk) the security app that checks for init.rc modifications never reported "root found" again. I do not know of any other detectors for init.rc modifications.
mrspeccy said:
You're welcome. My module just runs the same code as riru-momohider for hiding init.rc modficiations. The sudden detection you mention may be a false positive of MagiskDetector. Since I installed the module (under Magisk Zygisk) the security app that checks for init.rc modifications never reported "root found" again. I do not know of any other detectors for init.rc modifications.
Click to expand...
Click to collapse
I see. Thanks for your reply.
Hi, I begin to think it is not a false positive from MagiskDetector when it shows init.rc is modified by Magisk. Because the work profile in my phone has very strong root detection logic, and I just now it detected root and wiped out my work profile automatically
While other bank apps, root checkers, and even Momo could not detect at that moment, MagiskDetector did report init.rc modified.
I saved the logs from MagiskDetector when 1) it did not report init.rc modified and 2) it reported init.rc modified and compared the details. What I found is that there is a line in the log from 2) which is not there in 1) :
svc name init.svc.mdnsd
Any idea what this service is and is it supposed to be hidden by InitRcHider?
mrspeccy said:
....The sudden detection you mention may be a false positive of MagiskDetector.......I do not know of any other detectors for init.rc modifications.
Click to expand...
Click to collapse
dohanin said:
....I begin to think it is not a false positive from MagiskDetector when it shows init.rc is modified by Magisk....What I found is that there is a line in the log from 2) which is not there in 1): svc name init.svc.mdnsd...
Click to expand...
Click to collapse
i installed the module. it didn't work on reboot. i mean, MagiskDetector app reported 'modified'. i then cleared cache and data for MagiskDetector and ran the app; it asked me to 'reboot and try', which i did. now, it says 'not modified'. thanks!
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
It works, thanks.
yes, clearing data and cache of MagiskDetector sometimes work, but sometimes I had to re-install initrchider module in Magisk as well.
still puzzled on why after it worked, after a day or two, MagiskDetector would suddenly report Init.rc modified, without me changing anything or even reboot
dohanin said:
yes, clearing data and cache of MagiskDetector sometimes work, but sometimes I had to re-install initrchider module in Magisk as well.
still puzzled on why after it worked, after a day or two, MagiskDetector would suddenly report Init.rc modified, without me changing anything or even reboot
Click to expand...
Click to collapse
Apparently does this without magisk even installed which is why canyie commented that test in MagiskDetector is broken... When asked by @osm0sis if will be fixed vvb2060 said MD is deprecated / he she is working on Momo now... PW
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
On Android 11+, there maybe also init.svc_debug_pid.******
need resetprop --delete init.svc_debug_pid.$1
Work this Samsung Android 8.0, 9.0 Pie ?
This module does not work on Samsung Galaxy S7 edge Custom Pie 9.0 Rom, module active and magisk detector app and momo app shows nothing hidden
Zygisk - Shamiko lastest version now includes hiding init
huskydg said:
Zygisk - Shamiko lastest version now includes hiding init
Click to expand...
Click to collapse
Magisk Detector Test still show "init.rc has been modified by Magisk". Any configue.
z1022 said:
Magisk Detector Test still show "init.rc has been modified by Magisk". Any configue.
Click to expand...
Click to collapse
Detect modified init.rc is not always correct, so i think nearly there are no app detect it
Magisk detector shows once hidden init.rc and over time shows modified. The most reliable application detecting system modifications is MOMO 4.0.1 APP, it always shows if init.rc is modified, and if not it does not.
Spartacus500 said:
Magisk detector shows once hidden init.rc and over time shows modified. The most reliable application detecting system modifications is MOMO 4.0.1 APP, it always shows if init.rc is modified, and if not it does not.
Click to expand...
Click to collapse
I use MOMO 4.0.1 APP, it shows init.rc is modified. How can I fix it ? If I have already used Shamiko and InitRChider.
z1022 said:
I use MOMO 4.0.1 APP, it shows init.rc is modified. How can I fix it ? If I have already used Shamiko and InitRChider.
Click to expand...
Click to collapse
What phone model do you have ? I have Samsung Galaxy S7 edge 9.0 Pie and on Shamiko module it doesn't hide init.rc.
Just ignore because detect init.rc not always correct. I don't use initrc hider but momo don't detect it
mrspeccy said:
Several banking and security apps discover system modifications that Magisk injects through the init.rc file. These modifications can be successfully hidden with MomoHider (https://github.com/canyie/Riru-MomoHider), however, that module requires the Riru framework, which is incompatible with the upcoming Zygisk version of Magisk (e.g. Canary 23015). Therefore, I made a module that exclusively runs the init.rc hiding code from MomoHider without requiring Riru. See the attached file.
Just flash the module through the Magisk app. There are no configuration options. If the module is active, the init.rc hiding code is run.
I use the module to hide my custom Android ROM and Magisk from a recent app developed by the Danish Agency for Digitisation.
Click to expand...
Click to collapse
Hi @mrspeccy,
is your module source somewhere public? The Module is not working on my Device (AL10 Oreo 8.0.0) so I would like to look into it. Also it seems to be a good starting point for another Module Project. Injecting custom *.rc and fstab files without editing the ramdisk image.
Cheers
NewBit