I have a stock room, rooted with magisk, I checked the settings, SE for Android: permissive, when checking with getenforce: permissive, I also have several Xposed modules installed, and substratum, plus fully debloated, and v4a installed. I will post a link and instructions to flash the TWRP restorable rom( yes TWRP restorable) and I hope this works for you guys. There are much more possibilities with an permissive selinux.
Autocorrect.... *Rom not room
Update:
Because of the substratum themes I have installed, the power menu does not work properly.
A list of Xposed modules preinstalled on this OS:
Gravitybox(MM)
WanamXposed
Android N-ify
Burnt Toast
_________________________________________
Xposed Version: 87.1 Custom Wanam build( for Samsung rom support)
_________________________________________
Substratum themes installed:
Material glass
Pixel UI
_________________________________________
Magisk version: 15.2
_________________________________________
Other pre installed apps:
ES File Explorer Pro
OGYoutube + MicroOG module
Gboard ( to replace stock keyboard)
Action Launcher ( to replace stock launcher)
_________________________________________
I will upload the link a little later because of slow upload speed....
Here is the link to the TWRP Restorable Rom
https://mega.nz/#!HYMUTDyI!UZZydjyNdcs2q9jNLwbhveH8fyd-PqzfJVGQ2iFSC_Y
And the link to the Magisk Patched boot image ( J3 Emerge Sprint only!!)
https://mega.nz/#!yQcUiJyR!_KzFUzuEZ1UNhsBPmzQ8woA8umEXjsJO4gYmiEITOUM
When restoring select all options, then press restore, after that flash the patched boot image using TWRP, then flash the Magisk zip, and the no encrypt zip by ashyx, when flashed reboot system and you should be done! If anything goes wrong post down below.
To be honest, i think this should go under the roms section...
also, one key thing i almost forgot, you need to first create a backup in twrp, then place the folder inside the zip into the folder under your serial number created by TWRP during backup
Can anyone help solve the wifi problem??
Can you repost the download links
does it matter if you use supersu or magisk?
i got permissive kernel using magisk
you need to create a patched boot image using magisk and then flash in twrp, this will make ur kernel permissive
Related
It tries to load the framework and then it says Gravitybox has stopped working, it will close now.
The same problem as here:
http://forum.xda-developers.com/showthread.php?t=2529641
That fix didn't work for me.
Doesn't work on stock ROM
Sent from my Pixel C using Tapatalk
xposed and gravitybox also work sin stock rom.
use xposed v 82 sdk 32
and before you flash it use selinuxmodechanger.
you also can read it on the xposed thread.
xposed needs permissive selinux mode
and our kernel has enforcing mode. thats why it dont work
I have Xposed already installed.
skeleton1911 said:
xposed and gravitybox also work sin stock rom.
use xposed v 82 sdk 32
and before you flash it use selinuxmodechanger.
you also can read it on the xposed thread.
xposed needs permissive selinux mode
and our kernel has enforcing mode. thats why it dont work
Click to expand...
Click to collapse
Hi
Rooted stock rom.
From the official xposed xda page, I installed xposed installer, then flashed framework sdk23 (marshmallow), arm64 v84.
Xposed says 'not compatible with sdk version 23 or your processor architecture (arm64-v8a)'.
Is it the selinuxmodechanger that i haven't installed (yet) or will v84 not work anyway?
arlrb said:
Hi
Rooted stock rom.
From the official xposed xda page, I installed xposed installer, then flashed framework sdk23 (marshmallow), arm64 v84.
Xposed says 'not compatible with sdk version 23 or your processor architecture (arm64-v8a)'.
Is it the selinuxmodechanger that i haven't installed (yet) or will v84 not work anyway?
Click to expand...
Click to collapse
You're using the wrong version of xposed installer, you need v3.0-beta4.
Jonny said:
You're using the wrong version of xposed installer, you need v3.0-beta4.
Click to expand...
Click to collapse
Thank you, Jonny.
In case anyone else runs into this problem, it's the material design version by DVDandroid.
If you have any other version already installed, uninstall it first.
arlrb said:
Thank you, Jonny.
In case anyone else runs into this problem, it's the material design version by DVDandroid.
If you have any other version already installed, uninstall it first.
Click to expand...
Click to collapse
So, you downloaded the app and clicked on INSTALL/UPDATE with framework "xposed-v84-sdk23-amd64" and that's it?
xposed Qs
llucax said:
So, you downloaded the app and clicked on INSTALL/UPDATE with framework "xposed-v84-sdk23-arm64" and that's it?
Click to expand...
Click to collapse
Yes, that was it. It will auto-shutdown & auto-flash in TWRP, then restart & it should be done.
However, xposed installer says, in green, that sdk23 arm64 is active, yet, i'm not sure if a couple of modules i've tried are working properly/at all.
Minminguard module (ad blocker) for instance says that xposed is not enabled, & sure enough ads are still popping up in apps & in chrome.
So i'm wondering if certain modules won't work seeing as i'm using the latest installer & sdk/64? ie do the module developers need to keep up?
Can someone shed some light on how it works in that respect?
Should i try the 32bit sdk? (all 32bit sdks will work on a 64bit cpu, won't they?)
Or should i try a different version - 82?
Is there a version that is most reliable for most modules?
Same results in here, I guess we have to change the SELinux mode somehow for it to work according to what I've read somewhere else...
llucax said:
Same results in here, I guess we have to change the SELinux mode somehow for it to work according to what I've read somewhere else...
Click to expand...
Click to collapse
As skeleton1911 wrote "and before you flash it use selinuxmodechanger". That fixed most of my problems, I also use xposed V84, haven't tried V85 though
there is a solution for xposed by skeleton1911
---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------
skeleton1911 said:
Guys
there is a solution for xposed:
1. with mixplorer go to system/etc/init.d/ 07permissive and open it with editor (just tap on it)
2. remove the sleep 60 line. save and reboot to recovery
3. flash xposed framework , reboot and install xposed app and your modules. enable them in xposed app and reboot (normal xposed procedure)
4. open your apps like gravitybox etc.. ( they will connect to the xposed framework now)
5. open 07permissive again in system/etc/init.d and add sleep 60 into it again
6. save and reboot
Done!
in short words:
the cause is permissive and enforcing. Xposed only run in permissive mode on boot , but permissive mode forces some apps to close , but it is needed for viper v4a so i did this init.d script, system boots in enforcing and after 60 sec it will switch to permissive.
this is a dirty but working method. there is no other way at the moment because elephone didnt released the kernel source to modify it..
1. remove sleep 60 in 07permissive , save and reboot
2.perform the xposed stuff and after reboot open all xposed apps so they can connect to the xposed framework
3. add sleep 60 back into 07permissive and reboot
All works now!
cheers!
p.s: I will make a flashable zip for that soon
Click to expand...
Click to collapse
Do it anybody probe it? Maybe Do it working?
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Aha, thanks, I didn't know what is the difference
Jtig said:
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Click to expand...
Click to collapse
Mmm, OK, maybe is the soft reboot what I missed, because I used selinuxmodechanger and it didn't work with a full reboot. I am using stock but with RodriguezMod, but I think I will try the Eragon ROM. I'll report back. Thanks!
I'm finally trying the Eragon ROM, and following the steps from skeleton1911 finally seem to be working! At least Amplify for the first time is not complaining about not having Xposed. So I wiped, flashed the ROM, updated the SuperSU binary, rebooted, remove the sleep from the init.d script, went to the Xposed installer Material beta, updated from v82 to v85 using the installer, and after that flash, Amplify started to recognize Xposed!
Jtig said:
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Click to expand...
Click to collapse
That fixed it, thanks.
1. Substratum working partially...all themes working but don't apply overlays on Android system which will cause bootloop and as of now it's not supported...use cautiously link - https://www.xda-developers.com/top-substratum-themes-for-may-part-2/
3. Terminal Emulator
4. Greenify
5. Titanium Backup
6. Root explorer
7. Set CPU
8. Xposed framework and modules https://forum.xda-developers.com/moto-e4/themes/root-apps-moto-e4-t3659409/post73477433
guys report working apps if u find it more and will be updated after check
Unless the rules changed, you aren't allowed to mention or discuss lucky patcher at all, under any circumstances.
I had already sent him a PM about it, he'll fix it when he gets back or if a mod sees it. If I was a mod I'd remove it.
@KyleBryant kindly share and provide link for installing xposed framework and working modules on our device.
This is the Xposed for nougat thread:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
And this is a list of modules that work:
https://forum.xda-developers.com/xposed/unofficial-list-modules-nougat-xposed-t3639615
KyleBryant said:
This is the Xposed for nougat thread:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
And this is a list of modules that work:
https://forum.xda-developers.com/xposed/unofficial-list-modules-nougat-xposed-t3639615
Click to expand...
Click to collapse
Should select classic>SDK 25 zip and if uninstaller > arm64 zip right?
Yup
Guys anybody tried hidden weather widget which is activated under labs menu in Nova launcher? It's force close the launcher for me
WiFi tether router by Fabio Grasso
drganbds said:
Should select classic>SDK 25 zip and if uninstaller > arm64 zip right?
Click to expand...
Click to collapse
My E4 is arm64 but Android 7.1.1 is running under 32 bit mode on my phone, I had to use SDK25 arm for both the framework and the uninstaller, just a piece of advise
After Xposed had been installed on my Moto E4 woods_f with root access and Magisk v19.3 installed, it presented bootloop after flashing and frozen on the boot screen then. Even after reinstalling and giving Wipe Dalvik and Cache the problem persists.
Google has recently launched the Tez app for India, which supports payments from banks using UPI.
I tried installing it on my OnePlus X, rooted with xposed framework, Oxygen OS. It gives the message -
Tez can't be used on this device.
Click to expand...
Click to collapse
We've detected software running on your device that may not be secure.
Click to expand...
Click to collapse
I tried searching for solutions which generally end up with - Unroot your phone.
I tried RootCloak, doesn't help.
I don't want to unroot my phone, but I want to install this app.. it's getting quite popular among my friends.
So is there any other way to truly hide my root status for installing this app?
Root ur phone using magiskSU and hide root to tez by magisk hide.
Your device have to pass the safety net check for TEZ to work ,install safety net checker from playstore and test
On OOS it should work with Magisk SuHide option activated.
Remove Xposed forever. And would be better never ever use your rooted device for banking activity.
Unrooting or removing Xposed framework does not gives excuse to run Tez app. I have experienced. As your phone has the custom ROM, you cannot use Tez on your device. You have to completely install vendor's Official firmware on your device
i have no issue with magsik
On my OPO running COS 13.1.2, this is how I got it to work:
• Install Tez from PlayStore
•Disable the Xposed module within the Magisk Manager
•Goto Magisk Hide in Magisk Manager and select Tez to hide
•Disable the Xposed framework within the Xposed app
•Reboot phone
•Open Tez
I have found that once I successfully opened Tez and linked my profile and Bank Account, I could re-enable Xposed and still use Tez after rebooting
If the above process doesn't work for you, unroot your phone, and root it again with Magisk Manager, instead of flashing Chainfire's SuperSu
Follow simple steps -
1. Just uninstall xposed framework (No need to remove exposed installer)
2. Register tez / BHIM (dismiss root notifications)
3. Reinstall / update xposed framework.
I was facing issues during registration process only and im not using any third party app to hide root.
Now both are working fine.
Run Tez or any other secured apps on rooted device:-
I had the same problem with my rooted phone and magisk didn't do their part or we can say unsuccessful.
So I tried this and it works...?
Caution:- Follow step-by-step.
1. First download these three apps(in external card):- (Download all in recovery bootable zip )
1(a). SuperSu v2.82 RS3 (Recovery Flashable) :-
1(b). SuHide v1.09 Lite (Recovery Flashable) :-
1(c). SuperSu Config Aroma File v1.00 (Recovery Flashable) :-
2.Now root your device in TWRP mode
2(a). Select supersu config file and install it in "systemless SBIN mode" (modes showed when you start installation) and then leave all the other options default.
2(b). Install SuperSu into twrp boot mode.
2(c). Reboot once into android (or main screen) then again reboot it in recovery mode.
2(d). Install SuHide into twrp boot mode.
3. Reboot your device normally.
4. Open SuHide find the app which you want to use in rooted device and press right button (front of that app) till it changes to slash(/?️) eye or pirated eye.
5. Now use that app.
Note:- Succesfully Tested on MOTO G4 PLUS with given versions (if lastest version does not work use this versions only).
Kindly Check This Thread https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
Hola Amigos,
I have A Mido (2GB RAM) device with Superior OS (Phoniex,Android Q) Installed.I installed Magisk and whenever I flash any modules,
Magisk Crashes(Not Magisk Manager).Here's what I mean:The wallpaper I apply using Magisk get reset to default one.
Many Automatic Modules(Modules that start woring on boot) stop for 5-10 seconds and then work. App that I was using before the
crash also crashes.
It happens pretty frequently.
I installed Magisk like this:
Booted to TWRP
Wiped System,Dalvik,Vendor,Data,Cache
Formatted Data
Flashed Superior OS,Open Gapps Pico A10
Rebooted to System
After setting up Google
Rebooted to TWRP
Flashed Magisk 24.3.zip
Rebooted to System.
Installed Each Module one at a time and Rebooted,Then installed second module.....
Sometimes even of I don't install any module the Magisk Manager crashes.
The Modules that I use:
Google Sans Font System Lessly : https://www.pling.com/p/1457664/
MIUI Wallpaper and Akira Wallpaper(Live) : https://www.pling.com/p/1423749/
JamesDSP : https://zackptg5.com/downloads/jdsp_v4.4.zip
XDA Thread of (JamesDSP) (This is not a module): https://forum.xda-developers.com/android/apps-games/app-reformed-dsp-manager-t3607970
Naruto Sharingan BootAnimation for all devices : https://www.pling.com/p/1595951/
Godspeed Mode V X7 All devices : https://www.pling.com/p/1596710/
I am on stock kernel and TWRP 3.5.1
How can I fix these Crashes??
Also Fingerprint and auto rotate sensor are not working even if I uninstall Magisk,Whereas it works if I use UBPorts
Alpha V 1.1
Thanks for help!!!
I have same problem since I updated magisk to 26.1 and when I downgrade it to 25 or 24 stell same problem I tried to change magisk to kernel su the new root app and when I try to add one module at least It makes my app crash but it work only to give root access to any app I want and it is hidden from any app can detect root like bank apps this is crash log of one app of though apps https://bin.kv2.dev/~645360ede599576ea02c5490
And the screen shot the tree apps that crash when use modules
Mady_H said:
I have same problem since I updated magisk to 26.1 and when I downgrade it to 25 or 24 stell same problem I tried to change magisk to kernel su the new root app and when I try to add one module at least It makes my app crash but it work only to give root access to any app I want and it is hidden from any app can detect root like bank apps this is crash log of one app of though apps https://bin.kv2.dev/~645360ede599576ea02c5490
And the screen shot the tree apps that crash when use modules
Click to expand...
Click to collapse
Turns out James dsp and boot animation modules caused the crashes . Safety Net fix and shamiko did not cause the crash . Maybe you could try uninstalling unnecessary modules , btw which modules do you use ?
LolFlasherNoob said:
Turns out James dsp and boot animation modules caused the crashes . Safety Net fix and shamiko did not cause the crash . Maybe you could try uninstalling unnecessary modules , btw which modules do you use ?
Click to expand...
Click to collapse
Iam using ahamiko and safety net fix and hide my app list and ls posed I tried to add zygisk on kernelsu and when I did that it made my apps crash again and I tried to add module to install metrolla dailer phone to record calls it made my apps crash and ls posed zygisk didn't make any thing
So what is common with zygisk for kernelsu and jsp and boot animation
+
I will try to clean install the rom and root again to see what is going on and try to flash new rom to see if it is common in another rom or not
Mady_H said:
Iam using ahamiko and safety net fix and hide my app list and ls posed I tried to add zygisk on kernelsu and when I did that it made my apps crash again and I tried to add module to install metrolla dailer phone to record calls it made my apps crash and ls posed zygisk didn't make any thing
So what is common with zygisk for kernelsu and jsp and boot animation
+
I will try to clean install the rom and root again to see what is going on and try to flash new rom to see if it is common in another rom or not
Click to expand...
Click to collapse
Consider this guide .
Although it's for redmi note 11 , the rom flashing part is universally applicable to all devices.
[GUIDE] LATEST/UNIVERSAL FLASHING GUIDE FOR TWRP,OTHER RECOVERY AND ALL ROMS [Spes/Spesn] Redmi Note 11
: Combined four How To Guide threads into one. Post #2 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[WINDOWS-Only] Post #3 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi...
forum.xda-developers.com