Related
Hi,
Sometimes in Lollipop some module don't work. Then, in my case I reboot to recovery and I touch the file "conf/disabled" for starting without Xposed. After that, I like to disable the module in the UI of the Xposed Installer App... but when the framework is disabled, this option is disabled.
Please, can you change this?
Thank you!
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
manos78 said:
Hi,
Sometimes in Lollipop some module don't work. Then, in my case I reboot to recovery and I touch the file "conf/disabled" for starting without Xposed. After that, I like to disable the module in the UI of the Xposed Installer App... but when the framework is disabled, this option is disabled.
Please, can you change this?
Thank you!
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
Click to expand...
Click to collapse
Why don't you just disable the module, reboot, enable the module again and reboot again? No need to place any files through recovery?
By the way: could you give us more information about your device, the Android version and the Xposed files you use? Those are important information, without them nobody might help you.
orville87 said:
Why don't you just disable the module, reboot, enable the module again and reboot again? No need to place any files through recovery?
Click to expand...
Click to collapse
Because the device don't boot (bootloop on the boot animation)!!!
So, in this case the ONLY solution is: boot to recovery, touch the "disable" file, reboot with Xposed disabled... and then: How to DISABLE the module? The UI is blocking the option of enable/disable modules when the framework is disabled!
Please, remove this arbitrious limitation in the UI.
Thank you!
Why don't you just delete the modules.list inside the
data/data/de.robv.android.xposed.installer/conf/
folder?
corncobman said:
Why don't you just delete the modules.list inside the
data/data/de.robv.android.xposed.installer/conf/
folder?
Click to expand...
Click to collapse
Good alternative, but this disables all modules and you lost the info related to enabled/disabled modules... or not?
manos78 said:
Good alternative, but this disables all modules and you lost the info related to enabled/disabled modules... or not?
Click to expand...
Click to collapse
Yes, this method disables all modules. But what info related to enabled/disabled modules are you talking about? Which modules have been enabled and which not?
... you lost the info related to enabled/disabled modules... or not?
Click to expand...
Click to collapse
Not. The list of which modules are selected and which are not selected are still shown. Just disable the offending module and reboot.
corncobman said:
Not. The list of which modules are selected and which are not selected are still shown. Just disable the offending module and reboot.
Click to expand...
Click to collapse
Then you recommend "delete this file" instead of "touch the disable file" for disable only the loading of the modules but enable the framework? Then, when rebooting the phone the module list will be re-created?
The module list will be created when you change the list, i.e. toggle one module on or off. The changes only apply when you reboot.
manos78 said:
Then you recommend "delete this file" instead of "touch the disable file" for disable only the loading of the modules but enable the framework? Then, when rebooting the phone the module list will be re-created?
Click to expand...
Click to collapse
Do you want to permanently disable the module that causes the issue or do you want to use the module again after reboot?
In the first case, you can delete the corresponding module by using the in-build file manager of your recovery. Just navigate to /data/app and delete the module's folder. Done.
Otherwise, you only have the limited options presented to you (but I don't know why someone would continue using a module that is causing issues again and again).
orville87 said:
Do you want to permanently disable the module that causes the issue or do you want to use the module again after reboot?
In the first case, you can delete the corresponding module by using the in-build file manager of your recovery. Just navigate to /data/app and delete the module's folder. Done.
Otherwise, you only have the limited options presented to you (but I don't know why someone would continue using a module that is causing issues again and again).
Click to expand...
Click to collapse
Hi, I agree!
However, when a module "fails" I don't like to uninstall it... I like only to disable it. Why? Because I like to contact with the author and try fix the bug. Sometimes the problem is an update, o some other times the module is part of an App that has another functionalities. Then the best option is disable the module and not uninstall/remove it.
So, my concern is related to the best option to fix a bootloop when a module is creating some interference. Until now my best option is disable the Xposed framework, but here the recomendation is disable the load of modules. In this last case, I need to know if this file is re-created by the Xposed framework. And however, I feel is a good recomendation to enable the UI of the modules when the framework is disabled... the current behaviour is annoying.
Regards!
manos78 said:
Hi, I agree!
However, when a module "fails" I don't like to uninstall it... I like only to disable it. Why? Because I like to contact with the author and try fix the bug. Sometimes the problem is an update, o some other times the module is part of an App that has another functionalities. Then the best option is disable the module and not uninstall/remove it.
So, my concern is related to the best option to fix a bootloop when a module is creating some interference. Until now my best option is disable the Xposed framework, but here the recomendation is disable the load of modules. In this last case, I need to know if this file is re-created by the Xposed framework. And however, I feel is a good recomendation to enable the UI of the modules when the framework is disabled... the current behaviour is annoying.
Regards!
Click to expand...
Click to collapse
Ah, I see your point there. Well, I have some thoughts about another possibility. I haven't tried it yet, so no guarantee can be given if this will work. But before updating a module, you could backup the folder of the module from /data/app and place it's backup folder somewhere else. Then update the module and reboot. When facing a bootloop, just use the recovery file manager to replace the new files of the module with the old ones and reboot. This way one does not have to disable all modules or even disable/uninstall the entire framework.
orville87 said:
This way one does not have to disable all modules or even disable/uninstall the entire framework.
Click to expand...
Click to collapse
Yes, but I like the most simple option: At time, I do this when bootloop:
a) Reboot to recovery.
b) Open Aroma File Manager.
c) Rename "_disabled" to "disabled" in the xposed/config directory
d) Reboot
And when the device boots, I like to "disable" in the Xposed App... the problem is the UI... it disables interaction when the framework ins't loaded. From my point of view is a mistake! Why force this? Any reason that I don't view?
Another option is remove the file with the list of modules, but I don't know if the Xposed App recreates this file after boot, and if it's maintains the selected/unselected list of modules (normally I have some modules installed but disabled... think on Apps with Xposed add-ons that I don't like to use!).
Any comment?
manos78 said:
Yes, but I like the most simple option: At time, I do this when bootloop:
a) Reboot to recovery.
b) Open Aroma File Manager.
c) Rename "_disabled" to "disabled" in the xposed/config directory
d) Reboot
And when the device boots, I like to "disable" in the Xposed App... the problem is the UI... it disables interaction when the framework ins't loaded. From my point of view is a mistake! Why force this? Any reason that I don't view?
Another option is remove the file with the list of modules, but I don't know if the Xposed App recreates this file after boot, and if it's maintains the selected/unselected list of modules (normally I have some modules installed but disabled... think on Apps with Xposed add-ons that I don't like to use!).
Any comment?
Click to expand...
Click to collapse
When you have deleted the module list from recovery, Xposed will not create a new list after the following boot process. You have to open Xposed Installer and disable/enable a module, then reboot. This time, Xposed will create a new module list (with exactly the modules states they had before deleting the module list file apart from the last modification you have done to trigger this recreation) and you are free to go. Nevertheless, a cumbersome solution.
I have no idea why one isn't able to interact with the checkboxes, but my best bet would be to prevent the user from thinking that Xposed is indeed active and modules are not working despite being enabled.
orville87 said:
I have no idea why one isn't able to interact with the checkboxes, but my best bet would be to prevent the user from thinking that Xposed is indeed active and modules are not working despite being enabled.
Click to expand...
Click to collapse
Ok. I understand this point... with this the user don't be confused.
So, why not add one option menu in the screen of modules for "enable changes" when the framework is disabled? This option implies "the framework is disabled, but you can change the options". This be user friendly and powerful at time.
What you think?
manos78 said:
Ok. I understand this point... with this the user don't be confused.
So, why not add one option menu in the screen of modules for "enable changes" when the framework is disabled? This option implies "the framework is disabled, but you can change the options". This be user friendly and powerful at time.
What you think?
Click to expand...
Click to collapse
Might be a good point, but you have to ask rovo89 for feature requests. But I highly doubt that he will implement such thing.
orville87 said:
Might be a good point, but you have to ask rovo89 for feature requests. But I highly doubt that he will implement such thing.
Click to expand...
Click to collapse
Well, I hope Rovo89 will read this and agree to implement... it's a very simple change in the UI. :fingers-crossed:
manos78 said:
Hi,
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
Click to expand...
Click to collapse
Not really complicated. If you've access to ADB simply do
Code:
adb shell sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/conf/modules.list
adb shell sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml
Change PACKAGE with the package name of the app.
The first command would disable only the module, not the framework, not the rest of the modules. The second command would make sure that when you open the Xposed app -> Modules, your module shows up as unchecked. The second command is not important but it is good to keep confusion at a distance.
If you don't have access to PC always, you can keep a script inside your sdcard or `/data` as
Code:
#!/bin/sh
sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/conf/modules.list
sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml
If you've TWRP, you can edit the file to change the package name and run the script without the need of a PC.
nomap_here said:
If you've TWRP, you can edit the file to change the package name and run the script without the need of a PC.
Click to expand...
Click to collapse
Thank you!
But quite complex! I prefer to "touch disable" for disable Xposed (fail safe boot mode) and in the UI of the App (when the Xposed is disabled) then enable/disable the ofending module. I feel is MORE SIMPLE and INTUITIVE!
I hope Tovo read this and change the UI. :fingers-crossed:
Hi guys, I currently have a chromium browser with built in adblocker. I would like the browser to use its own adblocker and not use the system host file from AdAway.
AdAway blocks certain links like Google shopping and Slickdeal links. I have tried to whitelist these links in AdAway, however, this causes lots of apps to display ads. Consequently, I would like to whitelist things on the browser end and use the AdAway host file for system wide ad blocking, within every other app.
That said, may a Magisk module be made where Chromium uses a blank host file and the rest of the OS uses a different one? Does an app/tweak/mod like this already exist?
Any assistance would be much appreciated. Thank in advance.
I know this isn't the answer you're looking for, but you could try Adguard instead. There are options to allow useful ads, such as Google shopping links and Slickdeals. If you use it in VPN mode you don't even need root. It never messes with your host file so it won't trip SafetyNet.
JRJ442 said:
It never messes with your host file so it won't trip SafetyNet.
Click to expand...
Click to collapse
Since when does an edited hosts file trip SafetyNet?
Didgeridoohan said:
Since when does an edited hosts file trip SafetyNet?
Click to expand...
Click to collapse
Isn't that the whole reason for systemless host files? That's the impression I was given.
JRJ442 said:
Isn't that the whole reason for systemless host files? That's the impression I was given.
Click to expand...
Click to collapse
Nope.
Keeping your system mods systemless doesn't have anything to do (directly) with passing SafetyNet.
Copy-pasta incoming:
I've said it before and I'm sure I'll say it again. The purpose of Magisk is NOT to hide root and pass SafetyNet (it's just a really nice feature); it's to make your system modifications systemless. You could use this to keep your devices ability to update through OTA, with a couple of extra steps. But, the main advantage for me (and it's the deal-breaker) is that I don't have to redo any of my system modifications after an update. These could be changing screen density, debloating system apps, systemising apps, changing prop values, etc. Before Magisk I could spend 30-45 minutes after an update just setting upp all the system tweaks the way I wanted it, only to realise a couples of days later I'd forgotten something. Now, with Magisk - flash the update, done!
Didgeridoohan said:
Nope.
Keeping your system mods systemless doesn't have anything to do (directly) with passing SafetyNet.
Copy-pasta incoming:
I've said it before and I'm sure I'll say it again. The purpose of Magisk is NOT to hide root and pass SafetyNet (it's just a really nice feature); it's to make your system modifications systemless. You could use this to keep your devices ability to update through OTA, with a couple of extra steps. But, the main advantage for me (and it's the deal-breaker) is that I don't have to redo any of my system modifications after an update. These could be changing screen density, debloating system apps, systemising apps, changing prop values, etc. Before Magisk I could spend 30-45 minutes after an update just setting upp all the system tweaks the way I wanted it, only to realise a couples of days later I'd forgotten something. Now, with Magisk - flash the update, done!
Click to expand...
Click to collapse
I thought I read in the Adaway thread some time ago altering the host file will trip it, maybe that was just with SuperSU tripping it rather than an altered host. Either way, my first post in this thread was an alternative to helping the OP with his issue of certain sites being blocked, so its valid. Adguard would be a great alternative to the problems he's having with sites being blocked.
I can do the module you want, but I haven't many free time this week.. I will see what I do
Deic said:
I can do the module you want, but I haven't many free time this week.. I will see what I do
Click to expand...
Click to collapse
This would be great. Please keep me posted!
Deic said:
I can do the module you want, but I haven't many free time this week.. I will see what I do
Click to expand...
Click to collapse
Was the module ever made?
I'd like to know exactly why XPosed trips the SafteyNet checks even when running as a Magisk module. Is there a change that's easy to detect? Is it not possible to isolate the changes to certain apps? I want all the technical details about this issue.
What I'm aware of after talking to some of the devs and reading in the forums
That google play service downloads Safteynet XML file which executes and checks for Xposed File modifications
I think its due to Xposed modifying the /system folder, and as magisk is "systemless", it doesnt do that.
loguhn said:
I think its due to Xposed modifying the /system folder, and as magisk is "systemless", it doesnt do that.
Click to expand...
Click to collapse
But there's systemless xposed which still triggers safety net. So it can't be just that.
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
kabso5 said:
What I'm aware of after talking to some of the devs and reading in the forums
That google play service downloads Safteynet XML file which executes and checks for Xposed File modifications
Click to expand...
Click to collapse
That doesn't tell me anything about what part of Xposed trips the checks though.
gudenau said:
That doesn't tell me anything about what part of Xposed trips the checks though.
Click to expand...
Click to collapse
safetynet checks the zygote, which xposed modifies to work, thats why it trips, be it system or systemless, it didnt used to. Safetynet has evolved
aer0zer0 said:
safetynet checks the zygote, which xposed modifies to work, thats why it trips, be it system or systemless, it didnt used to. Safetynet has evolved
Click to expand...
Click to collapse
I don't get how a root-level app can't fool a non-root level app such as Google Play into thinking nothing's rotten in Denmark :crying::crying:
cthulhu1987 said:
I don't get how a root-level app can't fool a non-root level app such as Google Play into thinking nothing's rotten in Denmark :crying::crying:
Click to expand...
Click to collapse
I'm sure if they could spoof the zygote, or force it back as a pass like the bootloader and kernel, they would have done it already. Root is not exactly the entire solution
aer0zer0 said:
safetynet checks the zygote, which xposed modifies to work, thats why it trips, be it system or systemless, it didnt used to. Safetynet has evolved
Click to expand...
Click to collapse
How exactly does it detect it though? There are several versions it in the wild.
Maybe @topjohnwu can explain better here
aer0zer0 said:
Maybe @topjohnwu can explain better here
Click to expand...
Click to collapse
he did: https://forum.xda-developers.com/showpost.php?p=73691464&postcount=4200
Systemless Xposed cannot pass SafetyNet!!! SN checks the running Zygote process, it is not as simple as unmounting the files to hide it!
Click to expand...
Click to collapse
lover said:
he did: https://forum.xda-developers.com/showpost.php?p=73691464&postcount=4200
Click to expand...
Click to collapse
Lol, already saw that (it was in my earlier explanation) I think others in this thread want a more nuts and bolts answer.
aer0zer0 said:
I think others in this thread want a more nuts and bolts answer.
Click to expand...
Click to collapse
That would actually be awesome.
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
aer0zer0 said:
safetynet checks the zygote, which xposed modifies to work, thats why it trips, be it system or systemless, it didnt used to. Safetynet has evolved
Click to expand...
Click to collapse
lover said:
he did: https://forum.xda-developers.com/showpost.php?p=73691464&postcount=4200
Click to expand...
Click to collapse
Sure it checks it, but what does it look for? I want to know exactly what it does, as I said in the first post.
gudenau said:
Sure it checks it, but what does it look for? I want to know exactly what it does, as I said in the first post.
Click to expand...
Click to collapse
I am not the right person to answer
Nice thread going on here. Hope someone could explain the anathomy of SafetyNet and how does it check Zygote.
gudenau said:
Sure it checks it, but what does it look for? I want to know exactly what it does, as I said in the first post.
Click to expand...
Click to collapse
I believe if anybody actually KNEW this answer, they'd be able to spoof it. It could be some kind of tamper-detection stuff on the level that serious hackers use (e.g. measuring execution time of an arbitrary method), or it could be specifically design to detect Xposed (it is opensource after all).
This is one of those things where if you have to ask the question, the answer is probably beyond your expertise.
I'm watching this talk from 34c3.
Maybe this would explain/help on under standing saftynet.
https://media.ccc.de/v/34c3-8725-inside_android_s_safetynet_attestation_attack_and_defense
I think topjohnwu already explained well enough. Since SN checks not the "file integrity" of Zygote but the integrity of the running Zygote process in memory, it makes the spoof very difficult.
Since Zygote is loaded very early during boot and is actually the base of all system and app process (this is also why XPosed is so powerful by modifying Zygote), so it's always running and it's not so easy to spoof the memory contents (including code and data area) of a running process from another process, so there SN is tripped always.
However since there Zygote is modified by XPosed, maybe someone can modify the Zygotes in such a way that will pretent the integrity and thus will not trip safety net (like some root kit for Windows) but how and if this can be done is entirely beyond my knowledge...
lssong99 said:
I think topjohnwu already explained well enough. Since SN checks not the "file integrity" of Zygote but the integrity of the running Zygote process in memory, it makes the spoof very difficult.
Since Zygote is loaded very early during boot and is actually the base of all system and app process (this is also why XPosed is so powerful by modifying Zygote), so it's always running and it's not so easy to spoof the memory contents (including code and data area) of a running process from another process, so there SN is tripped always.
However since there Zygote is modified by XPosed, maybe someone can modify the Zygotes in such a way that will pretent the integrity and thus will not trip safety net (like some root kit for Windows) but how and if this can be done is entirely beyond my knowledge...
Click to expand...
Click to collapse
I'd like to discover some technical details too. I wonder if it's possible to compile a ROM with modified zygote binary that chain-loads Xposed stuff or something like that. But I'd need to first find out what exactly Xposed Zygote does differently, and go through trial and error with modifying zygote sources to find what actually trips it.
Hello...
Dont use magisk manager that much...
Now I tried to delete some modules. But when I go on the bin to uninstall them, nothing happen...
Also all the modules say, the will be actualized when reboot.
Rebooted many times... Nothing changes
Someone know what to do?
I have this problem too.
All the modules have 'this module will be updated' and I can't uninstall certain modules like xposed sdk25.
What version or Magisk are your guys running? That sounds like an old bug that supposedly was fixed...
The solution would be to manually navigate to /magisk with a root capable file explorer, deleting the module folders and then reboot.
Mine is Magisk Manager 5.4.0 and Magis 14.0
Isn't it the actual version?
And what do I do because of the update message?
aleccino said:
Mine is Magisk Manager 5.4.0 and Magis 14.0
Isn't it the actual version?
And what do I do because of the update message?
Click to expand...
Click to collapse
Manually remove the modules, like I said in my last post. And then try again...
Confirmed. Above-mentioned solution worked. Magisk v14 has the problems with deleting modules inside the app.
Darayavahus said:
Confirmed. Above-mentioned solution worked. Magisk v14 has the problems with deleting modules inside the app.
Click to expand...
Click to collapse
Glad to hear it works. I spend so little time on the stable release that I forget what bug was fixed when. :laugh:
Didgeridoohan said:
What version or Magisk are your guys running? That sounds like an old bug that supposedly was fixed...
The solution would be to manually navigate to /magisk with a root capable file explorer, deleting the module folders and then reboot.
Click to expand...
Click to collapse
Many thanks for that!! I was stuck on boot loop after new module installation and couldn't get rid of it with couple of mentioned methods here.
Finally deleting module's folder via twrp worked.
Thank you again
Settings whole system up again wasn't an option at this time for me
deleted
Didgeridoohan said:
What version or Magisk are your guys running? That sounds like an old bug that supposedly was fixed...
The solution would be to manually navigate to /magisk with a root capable file explorer, deleting the module folders and then reboot.
Click to expand...
Click to collapse
Where is the /magisk folder?
---------- Post added at 01:52 PM ---------- Previous post was at 01:48 PM ----------
akhil51183 said:
Where is the /magisk folder?
Click to expand...
Click to collapse
Sorry, found it!
Where is the /magisk folder??? Not able to find it.
Dhruvsaija said:
Where is the /magisk folder??? Not able to find it.
Click to expand...
Click to collapse
In case you haven't figured it out yet (and for any future people trying to find the same info), the /magisk folder hasn't been used for a long time.
All Magisk files (including modules) can now be found in /data/adb.
Didgeridoohan said:
In case you haven't figured it out yet (and for any future people trying to find the same info), the /magisk folder hasn't been used for a long time.
All Magisk files (including modules) can now be found in /data/adb.
Click to expand...
Click to collapse
Clutch! :good:
rooted with magisk and i'm trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail. Anyone else?
Make sure AVB verity is unchecked in magisk then reinstall from the app
qman66 said:
rooted with magisk and i'm trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail. Anyone else?
Click to expand...
Click to collapse
If the pixel 4 is any like pixel 3 with its logical partitions you'll have to use magisk to add to system. Easy way download a magisk module. Then go to /data/adb/modules then the module you installed if u need to add to /system/app you might have to add the /app set permissions then add what is wanted set permissions then restart. easy way without having to make your on module you can always go to magisk thread an learn to make a module as well either way only way I've been able to do it on Android 10 which I reverted back to pie so much better in my opinion
virtyx said:
Make sure AVB verity is unchecked in magisk then reinstall from the app
Click to expand...
Click to collapse
It's always been unchecked
billyt1 said:
If the pixel 4 is any like pixel 3 with its logical partitions you'll have to use magisk to add to system. Easy way download a magisk module. Then go to /data/adb/modules then the module you installed if u need to add to /system/app you might have to add the /app set permissions then add what is wanted set permissions then restart. easy way without having to make your on module you can always go to magisk thread an learn to make a module as well either way only way I've been able to do it on Android 10 which I reverted back to pie so much better in my opinion
Click to expand...
Click to collapse
Ok I'm willing to do this. What module do I download exactly?
qman66 said:
It's always been unchecked
Click to expand...
Click to collapse
Strange
That's the only thing I know that could cause you're issue
Android 10 requires you to so any system changes through Magisk in a "systemless" manner. As mentioned above, it needs to be in a module. If you can't do it yourself, ask for help from one of the devs. If it is a common task that others could benefit from, create a thread with the request and I am sure someone will come through...
CyberpodS2 said:
Android 10 requires you to so any system changes through Magisk in a "systemless" manner. As mentioned above, it needs to be in a module. If you can't do it yourself, ask for help from one of the devs. If it is a common task that others could benefit from, create a thread with the request and I am sure someone will come through...
Click to expand...
Click to collapse
ok does anyone know?
bump
qman66 said:
ok does anyone know?
Click to expand...
Click to collapse
What exactly is the question?
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
qman66 said:
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
Click to expand...
Click to collapse
I think it needs to be done "systemless" with a magisk module. Maybe if you ask @Tulsadiver nicely, he might be able to give you a template or even make you up what is needed. If so and it's possible others might have used for it you could share it.
qman66 said:
trying to transfer a file into system/bin but when i click r/w in root explorer nothing happens and when i try to copy it from the sd card it says fail.
Click to expand...
Click to collapse
You are welcome to try this. Put your file in the vrtheme/system/bin folder. Leave the system folder alone. This is untested.
qman66 said:
Ok I'm willing to do this. What module do I download exactly?
Click to expand...
Click to collapse
BusyBox is the module I always use