Related
Hello.
After many many tinkering and a small hint from @rovo89, finally i can present you the first stable version of the grorkmod.
Added v1.7 LineageOS-Version
Fix for bluetooth
Updated Audio_policy.conf will be copied. Result is a working audio.
Click to expand...
Click to collapse
Added v1.0 LineageOS-Version
Until the fix is integrated in the Rom, you can use the LOS-Version for a working fm-radio.
The Fix will add the following rights to selinux:
system_app fm_device:chr_file {write, read, open, ioctl}
This is a quick'n'dirty way.
Click to expand...
Click to collapse
Added v1.1 lite
In this version the fix is the same, but the script dont need an installed superuser. Also it will leave the system untouched.
Ive tested this version with Eragon v4.0 (With Gravitybox as testmodule, guess what... its working. Ive NOT tested if magisks will work properly with banking apps. please do it for me.
Click to expand...
Click to collapse
Review betaversions
In the past versions i have tried to workaround the problem.
At projectstart i have seen many audit denies. I tried to eliminate them with injecting allows to the sepolicy.
This was a part of the little success i had with the first versions. The other part was to set the classes internally to permissive.
These two components and the "bootprocesshack", in which i changed the sepolicy-binary in root, made the beta versions working.
The problem in the beta version was always, that in some cases the workaround didn't worked.
Click to expand...
Click to collapse
Stable
After an hint that @rovo89 gave me, i saw the problem in seconds, and.... *FACEPALM*
I've saw the problem and didn't saw it anyway.....
For a reason i don't know (maybe it's just a fault from Elephone or mediathek?) they "forget" to setup the contexts files not correctly.
With this mod i fix the entries in the seapp_contexts and file_contexts.
This is the whole magic.
Click to expand...
Click to collapse
Installation
Wipe Dalvik/Cache
Install ROM
Install SuperSU
Install grorkmod
Install xposed
then boot to system
Click to expand...
Click to collapse
Have fun with a fully working ROM!
greetings
vsrookie
CREDIT / INSPIRATION
@Chainfire - for his overwhelming work. @rovo89 - for making apps bend like metal
@skeleton1911 - for making his rom and his work
@Mikos - for his setools for android
@Deepflex - for all the work done to our device
Click to expand...
Click to collapse
Download mod LOS-Version v1.7
Download mod v1.1 lite
Download mod v1.0
Alternative Download
alternative Download mod v1.0
older Versions:
Download mod LOS-Version v1.5
Download mod LOS-Version v1.0
Download mod v0.94
Mirror v0.94
Download mod v0.8
Download mod v0.7
Download mod v0.6
Download mod v0.5
old Projectdescription:
About
This is a solution to get the xposed framework running in enforcing mode AND keep it running after a reboot, dalvik cache wipe and installation of any app.
The main goal is for sure the working xposed framework in enforcing mode, but as we all noticed there are several issues that come with a script that only set the selinuxmode to permissive. That's the second part of this project, trying to not change the behaviour of apps like on stockrom.
Click to expand...
Click to collapse
Background
As i get the p9000 and installed eragon the first time, i installed the xposed framework as fast as i can and.... everything works? Installed modules and... nothing worked!? I tried some things to get it working, but with everything i tried, i had to take a smear.
Pretty annoying, isn't it?
I took a deeper look into selinux and tinkered.... and tinkered ... and tinkered!
Now i think it's time to share my stuff with this great community and i hope that i will help with my mod.
Click to expand...
Click to collapse
BEWARE/Disclaimer
If you don't know what selinux is, then i think you have to read a "little bit" about it. (pure linux stuff; non Android)
If you google it, then you find everything you need, to learn more about it. If you don't know what rooting is, then play Angrybirds instead.
Understand this:
SELinux is a abbreviation for Security Enhanced Linux. That isn't just a name, it's the programm.
With this mod you will loose the S in the name.
Please be sure you have made a backup from everything that's important for you.
I've done this mod in all conscience, but I'm not responsable for bricked devices. Realize it!
You have been warned! :good:
Click to expand...
Click to collapse
The idea behind
This mod installs setools binaries to /su/bin, so you use them on terminal with this mod. We need them to inject permissions to the sepolicy binary. The next problem is, that the original sepolicy is compiled into the kernel (rootfs). Thats why it will be overwritten on boot. If you inject permissions manually, they are gone with every reboot. So i wrote a script that injects permissions on boot to a patched (with superkernel) sepolicy binary and copy it to root.
Click to expand...
Click to collapse
Installing
Now the funny part! :highfive:
What you need
I tested this mod on Eragon v2.8 and Aerom V3.
So you need one of these Roms (i think it will also work on rooted stockrom and Darksense, cause the two three other based on stockrom)
superSu 2.74
xposed framework v85
and of course my mod (see the attachement).
How to
Download everything to your SDCard.
Make sure you have wiped your device, so you can start fresh. (I don't have tried, only to flash this mod.)
Dont reboot. If you reboot, then reboot into recovery again!
Install the rom of your choice. (If you install Eragon v2.8, then be sure to delete the script inside /system/etc/init.d)
Install SuperSu 2.74
Install XposedFramework v85
Install Grorkmod
After this step just reboot. And check if everything is fine.
If not then let me know!
Click to expand...
Click to collapse
XDA:DevDB Information
Grorkmod, Tool/Utility for the Elephone P9000
Contributors
vsrookie
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2016-09-17
Current Beta Version: 0.94
Beta Release Date: 2016-06-09
Created 2016-06-09
Last Updated 2017-02-17
Reserved
LineageOS-Versions
v1.7
- FIX for not working audio over Bluetooth.
LineageOS-Versions
v1.0
- FIX for not working FM-Radio
Stockrom-Versions
v1.1 (lite version; systemless)
- reworked the script, so it will run systemless
- init.d support don't implemented in this version
- old grorkmods wil NOT be removed. So you have to install this one from scratch.
v1.0 (STABLE RELEASE!)
- live patching seapp_contexts and file_contexts
- live patching sepolicy binary at flashing time, add some allows were missing
- add init.d support as supposed to be
- disabling old grorkmod versions at flashin time.
v0.94
- live patching sepolicy binary at flashing time.
- works on all stockbased Roms
- Add init.d support, if it is not implemented already (For Stockrom; busybox EXCLUDED; it has to be installed afterwards to /system/xbin).
Minor changes are:
- cleared out Installer
Current issues:
- sometimes it's lost on reboot. Workaround: just reboot another time, or shutdown phone and reboot again.
v0.8
tidied up scripts
changed hook for injecting sepolicy
v0.7
simplified script
fixed an issue if phone shutdown
v0.6
fixed logcat support in scripts.
v0.5
Beta release
What exactly does your mod do then?
Sent from my P9000 using Tapatalk
mrbubba999 said:
What exactly does your mod do then?
Sent from my P9000 using Tapatalk
Click to expand...
Click to collapse
Hi.
Thank you. Didn't noticed!
I've added "the idea behind" to the first post.
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
do you need the xposed app?
Hi.
What do you mean?
You have to install it for installing xposed modules. Just install it after boot.
Greetings
Vsrookie
Sent from my P9000 using XDA-Developers mobile app
ok, thanks. did a quick test with AeromV3. At first gravitybox, app settings, flat color keyboard* worked after a soft reboot. Ebay app also worked.
Then on next soft reboot there was 2 loops of optimizing apps and only gravity worked.
Shut off the phone and restarted, none worked. After what I have read that was expected.
Did a soft reboot in xposed,then loops of android is starting- optimizing app . after third loop i shutdown the phone and restarted. Then xposed did not work. Tried another soft reboot, this time no loop and xposed modules are working and ebay app works.
mangoman said:
ok, thanks. did a quick test with AeromV3. At first gravitybox, app settings, flat color keyboard* worked after a soft reboot. Ebay app also worked.
Then on next soft reboot there was 2 loops of optimizing apps and only gravity worked.
Shut off the phone and restarted, none worked. After what I have read that was expected.
Did a soft reboot in xposed,then loops of android is starting- optimizing app . after third loop i shutdown the phone and restarted. Then xposed did not work. Tried another soft reboot, this time no loop and xposed modules are working and ebay app works.
Click to expand...
Click to collapse
Hi.
Never tried to softreboot the phone. I will try and report back as fast as i can.
Did you made a clean install? Or dirty flashed the mod?
greetings
vsrookie
clean AeromV3 install. normal reboots do not work
Good I have 3 sim cards on same number the way I mess with my phones.
Hi.
Tried to softreboot the phone from xposed installer. That don't work, that's sure.
On Eragon normal reboots work. I will test with Aerom soon.
greeting
vsrookie
Sent from my P9000 using XDA-Developers mobile app
ok, will test eragon. It stopped working altogether now on AeromV3 after several soft reboots, shutdowns and normal reboots.
gravitybox seemed to work, but other modules seemed to stop. Disabled gravity but that did not seem to work.
Also the android starting, optimizing app message loops seems random.
Seems better on eragon. Works after normal reboot, and from powered off. Ebay also works.
edit2..
so after installing same apps and some reboots, xposed modules will not function sometimes. A few reboots and this time they came back working.
one app that does not work is amplify, maybe just coincidence but that one seems to brake the other when selected.
mangoman said:
ok, will test eragon. It stopped working altogether now on AeromV3 after several soft reboots, shutdowns and normal reboots.
gravitybox seemed to work, but other modules seemed to stop. Disabled gravity but that did not seem to work.
Also the android starting, optimizing app message loops seems random.
Seems better on eragon. Works after normal reboot, and from powered off. Ebay also works.
edit2..
so after installing same apps and some reboots, xposed modules will not function sometimes. A few reboots and this time they came back working.
one app that does not work is amplify, maybe just coincidence but that one seems to brake the other when selected.
Click to expand...
Click to collapse
Is your edit 2 referring to eragon 2.8?
yes.
3-4 reboots, and not working. 1 soft reboot and they came back.
so seems a luck of the draw when it works after a reboot.
mangoman said:
yes.
3-4 reboots, and not working. 1 soft reboot and they came back.
so seems a luck of the draw when it works after a reboot.
Click to expand...
Click to collapse
Thanks, I'll leave it for now.
I made a backup of my eragon before I did any xsposed stuff, I can install that for eBay etc ...
PS - so I can't install this with xposed already running?
mangoman said:
yes.
3-4 reboots, and not working. 1 soft reboot and they came back.
so seems a luck of the draw when it works after a reboot.
Click to expand...
Click to collapse
That s not true.... sorry.
I am on aeromv3 right now rebooted around 5 times (normal, not over xposedinstaller).
Everything works as expected. Even with amplify.
Do you use backuped Apps?
Greetings
Vsrookie
Sent from my P9000 using XDA-Developers mobile app
arlrb said:
Thanks, I'll leave it for now.
I made a backup of my eragon before I did any xsposed stuff, I can install that for eBay etc ...
PS - so I can't install this with xposed already running?
Click to expand...
Click to collapse
Hi.
You have to do a clean install of the Rom of your choice. Install newest supersu and xposed, install this mod.
Everything should work fine.
If it is not so, there is another Problem. Maybe backuped Apps?
Greetings
Vsrookie
PS: if you install Eragon, don't forget ti delete the initd Script.
Sent from my P9000 using XDA-Developers mobile app
yes, strange. At first on eragon it worked with reboots, but after a few of them not so much. Then soft reboots seemed to do the trick.
Right now got amplify working. This time did not enable it in xposed first, but rather ran the app then enabled it in xposed when it asked.
vsrookie said:
Hi.
You have to do a clean install of the Rom of your choice. Install newest supersu and xposed, install this mod.
Everything should work fine.
If it is not so, there is another Problem. Maybe backuped Apps?
Greetings
Vsrookie
PS: if you install Eragon, don't forget ti delete the initd Script.
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
They say you should flash the framework before installing the installer & modules.
So should I install this after framework but before installer, or after framework & installer?
mangoman said:
yes, strange. At first on eragon it worked with reboots, but after a few of them not so much. Then soft reboots seemed to do the trick.
Right now got amplify working. This time did not enable it in xposed first, but rather ran the app then enabled it in xposed when it asked.
Click to expand...
Click to collapse
Hi.
Can you give the new version 0.7 a shot?
I had issues if the phone shut down completely. At this point i had also no running xposed anymore.
Fixed this.
Now i can reboot also out of xposed installer.
Greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
arlrb said:
They say you should flash the framework before installing the installer & modules.
So should I install this after framework but before installer, or after framework & installer?
Click to expand...
Click to collapse
Hi.
This order:
wipe
install rom
install supersu
install xposed franework
install mod
boot
install xposed installer
install modules
activate them
restart phone
greetings
vsrookie
Sent from my P9000 using XDA-Developers mobile app
I know that in Marshmallow RRO support is available on stock roms. Will the themes function properly on Oxygenos 3? Currently on 3.1.2. Thanks in advance
Anybody? I'm curious about layers support on OxygenOS as well
Sent from my ONE A2005 using XDA-Developers mobile app
Doesn't seem to work, gets stuck in a bootloop every time I try.
As far as I remember from short period I had OP2, and even shorter I had OOS on it, Layers worked only partially, for apps that were not calling for colours from frameworks and frameworks layer was the problem a it was boot looping the phone or some other bug preventing from usage, I don’t recall exactly. That’s because of lack of custom RRO commits in OOS which are used in custom ROMs to make them fully themeable. You can apply a layer for an app and see if it works. If boot loop, go to TWRP, navigate in file manager to /system/vendor/overlays and delete that layer.
Layers worked for me. However enabling some framework layer resulted in bootloop. AOSP dialer+Contacts working fine.
Thanks for the info guys. Guess I'll flash a ROM later on.
Hello fellow OP3 owners;
I recently rooted my OP3 and am a noob when it comes to Layers. I've only ever used CM theme engine. I'd like to stay on Oxygen until the binaries for dash charging are released.
My question is, does Oxygen support Layers? Now that I am rooted is there anything special I might need to do to get it working?
Anybody with expertise to discuss is appreciated. Hope everyone is enjoying their new device as I am
Cheers!
Just installed layers manager and layers showcase from the play store and it worked. Sweet. It also doesn't trigger the safetynet check so if you are using systemless root, Android pay should still work. The downside though is that many layers on the play store don't list compatibility with the OP3 so many of them are harder to get from the showcase app.
Edit: Should mention I'm on OOS 3.1.2 with systemless SuperSU.
Sent from my ONEPLUS A3000 using Tapatalk
Every theme *should* work but I've noticed most ones that theme the "Framework" have issues such as not booting or rebooting when you get power menu style popups.
thebcooper said:
Every theme *should* work but I've noticed most ones that theme the "Framework" have issues such as not booting or rebooting when you get power menu style popups.
Click to expand...
Click to collapse
Have the same exact prob.
*edit2*
You need to "compile & active" your favorite theme 5-10 times. It's like gambling ??
https://plus.google.com/+MertSativa/posts/1C3c954TGHL
____________________________________________________________
*edit*
Confirmed: March update breaks Substratum on rooted stock Rom's and custom ROM's with OMS
____________________________________________________________
Hi guys,
I updated yesterday my Pixel (March Security Update & Pixel 2016) and after setting up I want to use the Swift Dark Theme (Center Clock for O don't work too). So Substratum compile everything without problem and after a reboot still everything white. Someone else have problems with Substratum?
Confirmed. It did break Substratum on a stock non-rooted phone. Not sure if the rooted ones still work. Hopefully the Substratum team will fix it soon.
harihacker said:
Confirmed. It did break Substratum on a stock non-rooted phone. Not sure if the rooted ones still work. Hopefully the Substratum team will fix it soon.
Click to expand...
Click to collapse
If I know this before I wouldn't update haha
Me too!!
Sh0X31 said:
If I know this before I wouldn't update haha
Click to expand...
Click to collapse
Me too!!
No problems here on rooted (Magisk v16) stock. I did have to apply the themes about 6-8 at a time, or I had issues like those described in the OP.
funkybrunk said:
No problems here on rooted (Magisk v16) stock. I did have to apply the themes about 6-8 at a time, or I had issues like those described in the OP.
Click to expand...
Click to collapse
Thanks man
Build and enable overlays..reboot..go back in to subs and select enable and Bam!! Took me a while of playing with it the last two days but this "seems" to work
Apply the theme.
Reboot.
Go back to Substratum (bind with andromeda if not rooted).
Apply the same theme again.
Mostly works!!
Reboot.
Enable again in Substratum.
All works!!
Note: Am on stock unrooted.
Sh0X31 said:
*edit2*
You need to "compile & active" your favorite theme 5-10 times. It's like gambling ??
https://plus.google.com/+MertSativa/posts/1C3c954TGHL
Click to expand...
Click to collapse
It actually is just a bug with Package installer in the March update.
Many people approached us and thinks this is a big problem.
Instead of constantly Building and Applying...
1. Install all overlays you plan to use (Build and Update)
2. Reboot
3. All overlays installed before the reboot can be enabled/disabled. If you build and compile again, a reboot will update it.
NOTE: Building overlays and installing them IS NOT the fix. Please do not spread that fix.
Sent from my iPhone X using Tapatalk
What was wrong with cm theme engine that we gave up on it
attention exertion said:
What was wrong with cm theme engine that we gave up on it
Click to expand...
Click to collapse
Nobody gave up on it, it died when cm died and Lineage haven't resurrected it...
@nicholaschum - apart from reverting the two commits (in six files) and building from source so that rebooting isn't necessary again, has a simpler alternative been found?
There were mentions of a couple of fixes in the designers chat but there were no references.
Spannaa said:
Nobody gave up on it, it died when cm died and Lineage haven't resurrected it...
@nicholaschum - apart from reverting the two commits (in six files) and building from source so that rebooting isn't necessary again, has a simpler alternative been found?
There were mentions of a couple of fixes in the designers chat but there were no references.
Click to expand...
Click to collapse
Just need to revert one file and one line only. You don't have to revert the security patch.
Seems like a lot of developers believe tampering with what a security patch committed is such a big deal. If they actually read the code, a one liner is easily doable.
nicholaschum said:
Just need to revert one file and one line only. You don't have to revert the security patch.
Seems like a lot of developers believe tampering with what a security patch committed is such a big deal. If they actually read the code, a one liner is easily doable.
Click to expand...
Click to collapse
The file and line to revert would be useful - as a themer building from source is new to me!
Spannaa said:
The file and line to revert would be useful - as a themer building from source is new to me!
Click to expand...
Click to collapse
Try this: https://github.com/VelvetProject/frameworks_base/commit/636d0fc93f497bab26f9198a69fb813c7c1931ca
nicholaschum said:
Try this: https://github.com/VelvetProject/frameworks_base/commit/636d0fc93f497bab26f9198a69fb813c7c1931ca
Click to expand...
Click to collapse
Thanks @nicholaschum, that's sorted it - no reboot necessary now :good:
I am facing so many issues.
Microphone not working, phone getting restarted frequently and hangs.
This is happening only after March update and the pixel team does not have a fix yet. Can't call this a flagship service. Customer service is very much cool and calm after thousands of pixels are almost dead for a few days till now.
No response from Google yet.
Using substratum through andromeda on stock beta oxygen os with april security patch. i am using only (swift black)
follow steps below to use theme again
* Follow these steps with your own risk , I am not responsible if any damage caused
1 You have to uninstall all overlays from substratum
2 update all apps , theme ,substratum from play store.
3 open substratum through andromeda desktop client. (only for non rooted)
4 Select theme and click on overlays which you want to install
5 Click on build & install (let the processing to be done)
6 After that all overlays appearing in pink color
7 Restart your device (if nothing happens follow further steps)
8 open substrarum again (use desktop client if non rooted)
9 Click on manager icon
10 enable select to toggle all overlays and click on change overlays states (placed in blue floating overlay button)
11 Reboot device again
BOOM all overlays are installed and apps themed perfectly.
I've recently noticed this trying to apply substratum themes since i updated to Android Pie. None of the overlays compiles or applies. No overlays in manager either. Most times compiling does not even give any errors. I've tried most themes that claim Android 9.0 support.
Any ideas on how to troubleshoot this issue?
Ad.Shk2 said:
I've recently noticed this trying to apply substratum themes since i updated to Android Pie. None of the overlays compiles or applies. No overlays in manager either. Most times compiling does not even give any errors. I've tried most themes that claim Android 9.0 support.
Any ideas on how to troubleshoot this issue?
Click to expand...
Click to collapse
What version of substratum are you using? And, what themes have you tried?
Badger50 said:
What version of substratum are you using? And, what themes have you tried?
Click to expand...
Click to collapse
Substratum 1001.
Tried pitch black, mono/art, flux, Swift dark.
When i complete the there it creates a .Substratum folder on my storage. But when i reboot, it's gone.
Ad.Shk2 said:
Substratum 1001.
Tried pitch black, mono/art, flux, Swift dark.
When i complete the there it creates a .Substratum folder on my storage. But when i reboot, it's gone.
Click to expand...
Click to collapse
Ah. Yeah version 1001 doesn't work on the P2XL. Uninstall the one you have, reboot, then use the one in the link. Also, when you build your overlays, select "build and update" then reboot, then enable them in substratum manager. Pitch Black works great. Be careful with the others especially when themeing system and system UI, they can shut your UI down. Pitch Black works on everything though :good:
https://drive.google.com/file/d/1S_2XmrGn8l5-zjnE24fvwPt8FiKnnt-b/view?usp=drivesdk
Badger50 said:
Ah. Yeah version 1001 doesn't work on the P2XL. Uninstall the one you have, reboot, then use the one in the link. Also, when you build your overlays, select "build and update" then reboot, then enable them in substratum manager. Pitch Black works great. Be careful with the others especially when themeing system and system UI, they can shut your UI down. Pitch Black works on everything though :good:
https://drive.google.com/file/d/1S_2XmrGn8l5-zjnE24fvwPt8FiKnnt-b/view?usp=drivesdk
Click to expand...
Click to collapse
This version keeps crashing constantly. Restart/rescue me don't help either.
Ad.Shk2 said:
This version keeps crashing constantly. Restart/rescue me don't help either.
Click to expand...
Click to collapse
Are you rooted? If not, then I'm afraid your outa luck
Badger50 said:
Are you rooted? If not, then I'm afraid your outa luck
Click to expand...
Click to collapse
Rooted of course ... But it's luck still apparently.
Same here as well.
Android 9 rooted
Flash kernel.
Substratum v1001
Multiple themes don't work. They appear to apply but the apps are not themed.
Working for me, Pie, Magisk v17.1, Flash Kernel, using Substratum v998. Are you doing Build and Enable, then rebooting, then toggling the overlay state? I'm using Ethereal for System (Pie support) and Swift Dark for some apps.
Officechris said:
Working for me, Pie, Magisk v17.1, Flash Kernel, using Substratum v998. Are you doing Build and Enable, then rebooting, then toggling the overlay state? I'm using Ethereal for System (Pie support) and Swift Dark for some apps.
Click to expand...
Click to collapse
I've tried v998 but it keeps crashing
Ad.Shk2 said:
I've tried v998 but it keeps crashing
Click to expand...
Click to collapse
Have you tried clearing app cache/data a couple times? As well as uninstall/reinstall?
Use 998 and dont patch the substratum app when you install the themes
xDakos said:
Use 998 and dont patch the substratum app when you install the themes
Click to expand...
Click to collapse
1001 working correctly here, on top of it being themed. 998 worked correctly here even when themed, so substratum itself likely isn't the issue. What theme are you using?
yeah im using 1001 fine aswell but 998 worked with a restart and 1001 doesnt even need a restart anymore. Try PitchBlack
Just updated from 998 to 1001, so far everything working as expected.. lets hope it stays that way!