I wish to get Snapchat on my Amazon Fire.
I have made the following modifications to the stock:
- Installed CyanogenMod
- Installed Xposed
How do I uninstall Xposed or hide it from snapchat? I know how to hide root.
llamasking said:
I wish to get Snapchat on my Amazon Fire.
I have made the following modifications to the stock:
- Installed CyanogenMod
- Installed Xposed
How do I uninstall Xposed or hide it from snapchat? I know how to hide root.
Click to expand...
Click to collapse
Xposed consists of two components plus whatever modules you installed:
- Xposed manager can be uninstalled like any other app
- Xposed framework is uninstalled via this tool
I don't understand the Snapchat connection.
Davey126 said:
Xposed consists of two components plus whatever modules you installed:
- Xposed manager can be uninstalled like any other app
- Xposed framework is uninstalled via this tool
I don't understand the Snapchat connection.
Click to expand...
Click to collapse
Thank you.
Snapchat will not allow you to log in or create an account if it detects either root or Xposed.
llamasking said:
Thank you.
Snapchat will not allow you to log in or create an account if it detects either root or Xposed.
Click to expand...
Click to collapse
Gotcha. It's only Xposed Framework according to latest reports. Fair number of workarounds but all involve some level of effort on your part. I understand the developers motivations but blocking root/Xposed/etc does little to address the underlying issue. Akin to expecting security with a cheap luggage lock.
Davey126 said:
Gotcha. It's only Xposed Framework according to latest reports. Fair number of workarounds but all involve some level of effort on your part. I understand the developers motivations but blocking root/Xposed/etc does little to address the underlying issue. Akin to expecting security with a cheap luggage lock.
Click to expand...
Click to collapse
You could try rootcloak2 with Automate and get the xposed toggler from the Automate community addon. If you need help I'll be around.
Uninstalling xposed
Davey126 said:
Xposed consists of two components plus whatever modules you installed:
- Xposed manager can be uninstalled like any other app
- Xposed framework is uninstalled via this tool
I don't understand the Snapchat connection.
Click to expand...
Click to collapse
Hello, I recently downloaded a stock rom for my alcatel pop 3 (5) 5015X but the rom is for 5015A but that's not why i'm here, the guy who I downloaded from has flashed xposed to the rom and I tried all the uninstallers and they didn't work is there any other way I can uninstall it?
Bleagle15 said:
Hello, I recently downloaded a stock rom for my alcatel pop 3 (5) 5015X but the rom is for 5015A but that's not why i'm here, the guy who I downloaded from has flashed xposed to the rom and I tried all the uninstallers and they didn't work is there any other way I can uninstall it?
Click to expand...
Click to collapse
You have to use the uninstaller for the version/make of Xposed you have installed.
Xposed uninstaller
DragonFire1024 said:
You have to use the uninstaller for the version/make of Xposed you have installed.
Click to expand...
Click to collapse
I have xposed framework 85 and app version is 3.0 alpha4 also none of the uninstallers worked for me on this site: http://dl-xda.xposed.info/framework/uninstaller/
Bleagle15 said:
I have xposed framework 85 and app version is 3.0 alpha4 also none of the uninstallers worked for me on this site: http://dl-xda.xposed.info/framework/uninstaller/
Click to expand...
Click to collapse
Did you try just the ARM zip? Use the top one dated for 2015. That should work with any OFFICIAL Xposed version. Just flash it using FlashFire. If you have one of the other unofficial Xposed makes, you'll have to search for the uninstaller via their appropriate websites.
1) Open FlashFire
2) Tap the + and add the uninstall zip
3) Tap + again and select wipe. Make sure ONLY cache and dalvik are selected then tap the check mark at top right
4) Make sure wipe is placed AFTER the zip
5) Tap flash
xposed uninstaller
DragonFire1024 said:
Did you try just the ARM zip? Use the top one dated for 2015. That should work with any OFFICIAL Xposed version. Just flash it using FlashFire. If you have one of the other unofficial Xposed makes, you'll have to search for the uninstaller via their appropriate websites.
1) Open FlashFire
2) Tap the + and add the uninstall zip
3) Tap + again and select wipe. Make sure ONLY cache and dalvik are selected then tap the check mark at top right
4) Make sure wipe is placed AFTER the zip
5) Tap flash
Click to expand...
Click to collapse
I have tried every uninstaller on that site. I'm using twrp to flash them and i get error: 1
I'm trying now with flashfire..
---------- Post added at 07:55 PM ---------- Previous post was at 07:05 PM ----------
Bleagle15 said:
I have tried every uninstaller on that site. I'm using twrp to flash them and i get error: 1
I'm trying now with flashfire..
Click to expand...
Click to collapse
flashfire didn't work either...
Bleagle15 said:
I have tried every uninstaller on that site. I'm using twrp to flash them and i get error: 1
I'm trying now with flashfire..
flashfire didn't work either...
Click to expand...
Click to collapse
You may (likely will) need to perform a full wipe and reinstall the ROM of your choosing.
Related
This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant
How soon? I'd like to try the assistant and I was thinking of doing the build.prop modification, but now that I saw this thread maybe I'll rather wait for this module.
Edit: Sweet module. Love it, worked as expected.
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
flindaman said:
This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant
Click to expand...
Click to collapse
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.
loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Will this be a magisk module still? Can it be undone easily?
loserskater said:
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.
Click to expand...
Click to collapse
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding
flindaman said:
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding
Click to expand...
Click to collapse
I couldn't get his to work. I probably am doing it wrong. But now on tap still shows up.
loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Flashed in TWRP on Nexus 6, no /cache/magisk was created and neither the properties have changed:
Code:
$ adb shell
shamu:/ $ getprop ro.product.model
Nexus 6
shamu:/ $ getprop ro.opa.eligible_device
shamu:/ $
Did it work on Nexus 6p?
loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A
Papote3 said:
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A
Click to expand...
Click to collapse
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.
shinobi26 said:
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.
Click to expand...
Click to collapse
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager
Papote3 said:
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager
Click to expand...
Click to collapse
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.
shinobi26 said:
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.
Click to expand...
Click to collapse
Does magisk manager have storage permission?
loserskater said:
Does magisk manager have storage permission?
Click to expand...
Click to collapse
It does. It's the only permission in fact.
If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).
stangri said:
If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).
Click to expand...
Click to collapse
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Edit2:
As you can see below, loserskater already posted the same thing in post 3.
So yeah ...
TAM1m said:
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Click to expand...
Click to collapse
This is exactly like my module in post 3 of this thread.
loserskater said:
This is exactly like my module in post 3 of this thread.
Click to expand...
Click to collapse
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
No worries, just merely pointing it out.
TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
Thanks for trying to help, but you probably missed this: http://forum.xda-developers.com/showpost.php?p=69088754&postcount=8 too.
Again, if anyone with Nexus 6 (or arm platform in general) got any cache modules working, please let me know.
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Edgar_M said:
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Click to expand...
Click to collapse
If you have disabled the framework, restart your device and uninstall the modul which makes problems
Imagine, you have installed a whole bunch of modules and you need to find out which one is causing the trouble ...
The installer just shouldn't disable the enable/disable checkboxes in the modules list on purpose in case of a framework not installed state and everything is fine. At least it was implemented like this pre 3.0
Edgar_M said:
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Click to expand...
Click to collapse
There is a flashable file to disable all modules from recovery
Sent from my SCH-R220
Edgar_M said:
Hi mattzeller! Thanks for your contribution to that topic. But please read the original post once again. Then you will see, that you are missing the point with your post. Not a big deal - let's just try to keep the good quality of XDA alive
Click to expand...
Click to collapse
I fully understand your original post. If you are in a boot loop because of a specific module, disabling all of them will ensure you get out of a bootloop without removing Xposed completely so you can figure out which one it is via logcat. If it is Xposed itself causing the bootloop, it doesn't matter what modules are installed or activated.
Sent from my SCH-R220
Hi,
Freshly installed Magisk today. I have tried to install the 'Sony Framework' module from (Seyaru Module by eric9401 work).
However as title it says 'Module will be updated at next reboot'. I can disable the module, but the option to delete using the trashcan doesn't work either. Has anyone else come across this with any tips to resolve?
I am running a galaxy s8
Thanks
stephenwatson2010 said:
Hi,
Freshly installed Magisk today. I have tried to install the 'Sony Framework' module from (Seyaru Module by eric9401 work).
However as title it says 'Module will be updated at next reboot'. I can disable the module, but the option to delete using the trashcan doesn't work either. Has anyone else come across this with any tips to resolve?
I am running a galaxy s8
Thanks
Click to expand...
Click to collapse
Some modules require full uninstall and reboot before you update them (AML, for example). To fix this, you'll have to uninstall Magisk and reinstall it and the modules you want to use. Make sure you download the update and that it's in your magisk folder before you uninstall everything.
BIGWORM said:
Some modules require full uninstall and reboot before you update them (AML, for example). To fix this, you'll have to uninstall Magisk and reinstall it and the modules you want to use. Make sure you download the update and that it's in your magisk folder before you uninstall everything.
Click to expand...
Click to collapse
Or u can manually uninstall modules from twrp if u have magisk mount already flashed. And the u go to magisk directory and deleted individual modules. No need to uninstall/reinstall magisk.
This is how I fixed it. I had same trouble with AML
TahirZX said:
Or u can manually uninstall modules from twrp if u have magisk mount already flashed. And the u go to magisk directory and deleted individual modules. No need to uninstall/reinstall magisk.
This is how I fixed it. I had same trouble with AML
Click to expand...
Click to collapse
Thanks. I was able to uninstall the modules this way. I still can't get the Sony framework working but i will keep trying
Dang.
Maybe good tip. My busybox had a red update mark but it was kind of working. Then i disabled modul, by doing i saw network sign (!) is gone so i "dicided" to full uninstall magisk.
Now my phone hang on bootlogo.
Not sure how to restore with flashfire backup i dumped. Maybe possible to push/install magisk manager via adb?
No twrp atm just stock recovery^^
Fixed by flashing magisk custom boot.img which was used to get root but now not able to install busybox modul :/
Switched to SuperSu busybox now working.
stephenwatson2010 said:
Hi,
Freshly installed Magisk today. I have tried to install the 'Sony Framework' module from (Seyaru Module by eric9401 work).
However as title it says 'Module will be updated at next reboot'. I can disable the module, but the option to delete using the trashcan doesn't work either. Has anyone else come across this with any tips to resolve?
I am running a galaxy s8
Thanks
Click to expand...
Click to collapse
Mount magisk through twrp remove it and update m
stephenwatson2010 said:
Thanks. I was able to uninstall the modules this way. I still can't get the Sony framework working but i will keep trying
Click to expand...
Click to collapse
I think it could be the module's problem, try this one: https://forum.xda-developers.com/ap...apps-enabler-systemless-t3620100/post77621189
... BUT canńot install... of course (typo).
Hi,
I'm on LineageOS 14.1, xposed 89, API25.
Phone is rooted, superSU grants root access to Xposed Installer.
Xposed-Framework version89 is active
I try to update my installed modules or install new ones, but I only can download them. After finished, nothing changes, the "download" button stays, nothing like an "install" button apperars. What am I doing wrong?
Cheers,
Wolf
Have you tried clearing the data/cache for Xposed Installer?
Sent from my Nexus 6P using Tapatalk
Curiousn00b said:
Have you tried clearing the data/cache for Xposed Installer?]
Yes; I did - did not work.
With more playing around I found this solution:
* uninstalled the installer
* downloaded the installer apk from here: https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299
* reboot - all fine.
Still, I do not really understand whether I need to install the zip AND the apk, or whether just one is good enough. Anyway - it works now.
Cheers,
Wolf
Click to expand...
Click to collapse
First, I hope this thread is in the right place and apologize if it is not.
I currently have the problem that the Magisk Manager shows the two categories "Superuser" and "Modules" grayed out at the bottom. In addition, it is also so that the settings of the manager is slimmed down (fewer functions than usual). For this I have 2 screenshots ready: (see attachment and sorry for the German language).
Root itself is still there though (the apps that ask for root still do).
But can imagine that this happened because of the Magisk Hide app. Because I had hid the manager under a different app name, then either accidentally deleted it or restored the original package (can't remember).
In any case, I have already tried to install the manager with an SD card with the TWRP (did not work) and to install Magisk Manager via the apps themselves (pressed install in the first screenshot). This has come the following error message:
Code:
- Target image: /dev/block/
- Device platform: arm64-v8a
- Installing: 24.1 (24100)
! Unable to check signature
! Installation failed
My current status is that this has already happened once with the manager - judging by the bug reports on Github. Can someone please explain me in simple steps how to get this fixed? Thanks!
Bump
JulianKlein said:
Bump
Click to expand...
Click to collapse
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.
V0latyle said:
No need to bump, your post was only 7 posts down, and only one bump is permitted every 24 hours.
The issue is clear from your screenshots. You don't have root. On the Magisk screen, at the top under the Magisk section, if "Installed" shows "N/A", you do not have working root. Magisk is unable to load modules without root.
Click to expand...
Click to collapse
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?
JulianKlein said:
Sorry, didn't know that.
But I don't quite understand. Why should I have no root if apps like Lucky Patcher, Vanced Manager ask for root and I can verify these requests with the manager?
Click to expand...
Click to collapse
I'm not sure. I think you can still manage root permissions if you don't have root but I'm not 100% on that.
I suggest re-rooting with the prescribed method for your device. On the Pixels, we just re-patch and flash the boot image.
i hace the same problem in sm a70, the apps request root acces and i press yes and work but if the same app need request more times for example unloking network , the request are send again and again and again
I just took the leap into Android 12 and we t through the process of patching the boot img and flashing it. I have the same issue as the op. I have patched, repatched, and flashed and reflashed at least 4 or 5 times now. No change.
Edit to note that I do in fact have root, regardless of what Magisk says (installed - N/A). Apps like AdAway have root access and are working properly.
I had the same problem on my (very) old J7 (2015).
Am on android 7, and was trying to update Magisk from v24.3 to v25.1
I had to completely remove Magisk, and restarted from scratch.
Flashed the v25.1 apk in TWRP.
Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!
constrito said:
Same problem with Magisk 52.2 on my LineageOS 19.1 (Android 12L) installed on GT-N8000 (Samsung Note 10.1). I already tried re-root, re-flash, re-install apk and nothing!
Click to expand...
Click to collapse
Do you originally have magisk hidden as another app then install mm anew?
Nergal di Cuthah said:
Do you originally have magisk hidden as another app then install mm anew?
Click to expand...
Click to collapse
I'm not sure about it, but I tried a few versions of Magisk and none worked. I installed both boot.img and magisk.apk via TWRP. The app downloaded and installed by Android always forces an upgrade.
constrito said:
The app downloaded and installed by Android always forces an upgrade.
Click to expand...
Click to collapse
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot
Nergal di Cuthah said:
That's because you haveca newer boot than the magisk manager.
Let it upgrade
Then tap the uninstall button
Restore images
Then complete uninstall
Reboot
Install magisk
Reroot
Click to expand...
Click to collapse
I don't have an uninstall button. I put a print screen in the previous post.
Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.
Nergal di Cuthah said:
Did you mean to post something if so you didn't
Click to expand...
Click to collapse
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.
constrito said:
Sorry if there was some confusion, here is: https://forum.xda-developers.com/t/...nd-superuser-grayed-out.4409627/post-88379373.
Click to expand...
Click to collapse
See my edit
Nergal di Cuthah said:
Did you mean to post something if so you didn't
Not sure what to say about no uninstall but i guarantee that you have a double install. Look through your apps. Did you ever hide magisk with a different name, you've got to remember that at some time you did.
Click to expand...
Click to collapse
I removed the Magisk via TWRP by flashing it with the uninstall.zip file. After installing the Magisk via flash with the Magisk.zip file and rebooting the tablet, I patched my boot.img, went back to TWRP, flashed the boot.img selecting the boot option and rebooted. I went back to the Magisk app and the same problem. I checked via
Code:
adb shell pm list packages | grep magisk
and it returns only
Code:
package:com.topjohnwu.magisk
it suggests I have only 1 app installed (none hidden).
Then I'm out of ideas sorry
Nergal di Cuthah said:
Then I'm out of ideas sorry
Click to expand...
Click to collapse
No problem and thank you.