Database Users

[GUIDE][XT1254]Getting Xposed Working

Guide: Getting Xposed Running​This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.

Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.

ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.

i dont need it but its a great guide, easy, short and with pictures!

Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.

Thanks so much man, about to flash. Will let you know how it goes.

Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours

It did not work for xposedbridge.jar

aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated

savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app

I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?

After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?

I am having same problem as u smokie

smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.

Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!

Thanks for this , works great , now we just need one with busybox preinstalled

Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse

so will doing this enable gravitybox to work on the turbo?

hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces

rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!

[WORKAROUND] Bootloops due leaking handles with Xposed in Lollipop

Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.

Excellent work friend @ondrejvaroscak. Congrats! Awesome

Was waiting a long time for this! Thanks man! working perfectly.

Working perfectly on D6603, thanks

I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button

Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?

Thanks Bro , Very Nice !!
Perfect Work !!

Z1, C6903
Thank you for this great solution, works on Z1.

NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app

norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..

Working on fully setup 5.02 on Z2 thanks.

ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa

hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).

Ok fine... for verify all you said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?

hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app

Great thanks

ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa

In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !

Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line

hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?

LG G2 (D800) IR Remote Control for 5.1.1 (CM12.1)

Hey all, not sure if this is covered somewhere else or not. My searching only seemed to yield results for 5.0. If it isn't, maybe this'll help some, if it is, please let me know of the better option.
In short, I upgraded from CM12 to CM12.1 yesterday. For the remote in CM12, I enabled init.d support and flashed the .zip in this link:
http://forum.xda-developers.com/lg-g3/themes-apps/app-quickremote-port-aosp-t2929146
Hereafter option A, lol.
That worked just great for me, no issues at all. When I upgraded to 12.1 yesterday, that didn't seem to work anymore. All I get is a quickremote force close message when the phone first boots. I tried these as well:
http://forum.xda-developers.com/lg-...app-cyanogenmod-12-nightly-t3048963?nocache=1
Hereafter option B.
Both .zips in option B yielded the same result. I tried the play store not really expecting anything, but found a remote called AnyMote - Smart TV Remote. It says it only works with the G3 and G4. When used with none of the quickremote .zips installed, it doesn't find the IR sender and won't do anything. With the quickremote .zip installed though (either one from option B, didn't try A), it finds the IR sender. I set up that app for my TV's etc, and its working perfectly so far. The only annoyance is I still get that once force close message upon first boot.
So in sum, what I did was set selinux to permissive with universal init.d.
Flash one of the .zips in option B in TWRP.
Install AnyMote from the play store.
All is well so far, I'll update if something changes. Also, feel free to tell me of a better option. I didn't find anything yet and this is what I figured out, but it doesn't mean it's the best.

Hello
Hello, first of all, thanks for pointing me in the right direction, since my first android smartphone (many years ago) i install custom roms on every phone i lay my hands on, stock roms are not enough having so many flavors of roms, personally i like cm more but sometimes it just does not work with some of my devices, in this case i have the ls980 variant of the LG G2, i installed cm12.1 and the system was ok, but i could not get to work the Quick Remote apk and the battery drained really fast, i switched to crDroid with 6.0 and the same 2 problems plus wifi acting weird, i was stuck with modded stock ZVG 5.0.2, with the lame lg garbage software, yesterday i found Resurrection Remix and i flashed it, it works like a charm, so i decided to give quick remote another try, i tried to set Selinux to permissive and toggle init.d but it seems that this is enabled by default in the rom, so i just flashed v2 of option b and boom, its working flawlessly, i also updated the Quick Remote apk with one someone uploaded in the comments of the same post, so it has the latest features, this is the only rom i could make it work in. anyways i just wanted to share my experience with this thingy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

CM13 MM
Hello, im here again to update the topic more, i now updated my G2 to Resurrection Remix on MM based on CM13, and the files that worked for me on 5.1.1 wont work on 6.0, so after asking some questions here and there, syndre, another user, found the necessary files for QuickRemote to work on MM, so i bring them here, i also want to explain the process because for me, it was not as straight forward as last time.
First and obviously you have to download the zip wich i will attach at the bottom
Second and more obvious, you flash the file on your custom recovery, it doesn't matter wich you have (twrp, cwm, philz)
Remember that your Selinux has to be set to Permissive wich you can maybe do in your rom settings, some of them have it by default set to permissive or you can search for the Selinux mode changer here on Xda, also your rom has to have init.d support enabled, again, some of them have it by default, you can download Universal Init.d from the play store and enable it,
The zip will flash the apk's for QuickRemote and QuicksetSDK and the files needed for them in /system/app, it will also flash a startup init.d script in /system/etc/init.d/ and another script in /system/addon.d/
The apk's (LGQRemote.apk and QuicksetSDK.apk) must have their permission set to rw-r--r-- or chmod644 both of them for the system to detect them, if they dont appear on your app drawer, unzip the file and manually copy them to their respective folders in /system/app/ using aroma file manager or Es File Explorer with root permission, you can chmod644 them on aroma file manager or set the permissions in Es File Explorer
The scripts (80-quickremote.sh and 10QuickRemote.sh) must have their permissions set to rwx rwx rwx or chmod755, this will almost never fail but if they do, you can do the same as with the apk's.
Every time you copy files or set permissions you have to reboot for the changes to take effect.
You should now have QuickRemote working on you AOSP MM build, if not, lets troubleshoot.
I can't see the quick remote app, be sure the apk's are on the right folder inside /system/app/ and that they have the right permissions set, also the app may be in the app drawer but its named com.lge.... and it has the default green android icon.
At boot it gives me a "QuisetSDK stopped working" error, remember to check your Selinux and init.d state, Selinux must be Permissive and if init.d is enabled you should se a file named Qremote.log on the root of your Sdcard, if you open it as text, you will see if the state of Selinux is correct, if you dont see the file, init.d is disabled and if you see it but it does not say that Selinux is permissive you have to set selinux to permissive.
I can open the QuickRemote app but no manufacturers are showing on x device list, this is a Selinux or init.d problem, do the previous 2 steps again.
Those are the only problems I've encountered, amd thats the way i solved them, if you have any more questions, send me a pm remeber to thank @syndre for helping to bring this to MM
Zip file uploaded to Mega

Jc_master said:
Hello, im here again to update the topic more, i now updated my G2 to Resurrection Remix on MM based on CM13, and the files that worked for me on 5.1.1 wont work on 6.0, so after asking some questions here and there, syndre, another user, found the necessary files for QuickRemote to work on MM, so i bring them here, i also want to explain the process because for me, it was not as straight forward as last time.
First and obviously you have to download the zip wich i will attach at the bottom
Second and more obvious, you flash the file on your custom recovery, it doesn't matter wich you have (twrp, cwm, philz)
Remember that your Selinux has to be set to Permissive wich you can maybe do in your rom settings, some of them have it by default set to permissive or you can search for the Selinux mode changer here on Xda, also your rom has to have init.d support enabled, again, some of them have it by default, you can download Universal Init.d from the play store and enable it,
The zip will flash the apk's for QuickRemote and QuicksetSDK and the files needed for them in /system/app, it will also flash a startup init.d script in /system/etc/init.d/ and another script in /system/addon.d/
The apk's (LGQRemote.apk and QuicksetSDK.apk) must have their permission set to rw-r--r-- or chmod644 both of them for the system to detect them, if they dont appear on your app drawer, unzip the file and manually copy them to their respective folders in /system/app/ using aroma file manager or Es File Explorer with root permission, you can chmod644 them on aroma file manager or set the permissions in Es File Explorer
The scripts (80-quickremote.sh and 10QuickRemote.sh) must have their permissions set to rwx rwx rwx or chmod755, this will almost never fail but if they do, you can do the same as with the apk's.
Every time you copy files or set permissions you have to reboot for the changes to take effect.
You should now have QuickRemote working on you AOSP MM build, if not, lets troubleshoot.
I can't see the quick remote app, be sure the apk's are on the right folder inside /system/app/ and that they have the right permissions set, also the app may be in the app drawer but its named com.lge.... and it has the default green android icon.
At boot it gives me a "QuisetSDK stopped working" error, remember to check your Selinux and init.d state, Selinux must be Permissive and if init.d is enabled you should se a file named Qremote.log on the root of your Sdcard, if you open it as text, you will see if the state of Selinux is correct, if you dont see the file, init.d is disabled and if you see it but it does not say that Selinux is permissive you have to set selinux to permissive.
I can open the QuickRemote app but no manufacturers are showing on x device list, this is a Selinux or init.d problem, do the previous 2 steps again.
Those are the only problems I've encountered, amd thats the way i solved them, if you have any more questions, send me a pm remeber to thank @syndre for helping to bring this to MM
Zip file uploaded to Mega
View attachment 3618886
View attachment 3618887
Click to expand...
Click to collapse
hello and thanks for finding a some more answers. I redid the zip I first posted that was broken and not able to be flashed. I took out the odex files too, I dont think that is necessary. I have tested this zip on two different AOSP 6.0 roms on my G3, and in each case all the permissions were correct and needed no manual setting afterwards. And of course, the quickremote app works , both blasting and learning signals!
my post about it is here

[FIX][ExtSD] ExtSD Fix (v2.9b - 2016-06-09)

Disclaimer: I am not responsible for anything bad that may occur from the use of this zip, but I will take all the credit you can give if it works for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ExtSD Fix​
Download latest stable - MD5 checksum​Download latest dev - MD5 checksum​
In KitKat, Lollipop and Marshmallow, policies on writing permissions for external SD cards have been changed. This flashable recovery file automatically appends the correct permissions to the file as explained in many tutorials on the web (here or here) or as what many apps do (here).
Advantages
The advantage of this flashable zip over the other methods is that:
you don't need to install any apps,
you can revert by reflashing (not tested for marshmallow),
it does not require you to have root (needs to be confirmed),
[*]you don't need a custom recovery (needs to be confirmed).
Installation
It can insert and remove the permission to write on the external sdcard. To install follow these steps:
Turn off phone,
Boot into recovery,
Backup your system and data partition,
Flash this zip file once,
Reboot phone normally.
To revert the changes, follow the same steps again. This means that flashing it twice will have no effect.
Marshmallow is not supported yet, implementation is in progress.
Note: On Marshmallow, busybox will be installed if not already present. It can also be installed as a standalone app. You should an also add init.d support to your phone if not already available using an app.
How to report a bug
Check if someone else reported that it did/didn't work,
Backup, clean flash, reinstall all apps and then flash ExtSD Fix,
Submit a bug report here with both the original and modified packages.xml and the recovery log file as suggested here.
Changelog
v2.9b - 2016-06-09
Added double flashing revert for MM.
v2.8b - 2016-06-09
Added more logging to:
during flashing: /data/ExtSD_Fix_RW_inst.log
during boot: /data/ExtSD_Fix_RW_initd.log
v2.7b - 2016-06-08
Renamed script,
Changed permissions.
v2.6b - 2016-06-07
Changed permissions.
v2.5b - 2016-06-07
Changed permissions,
Added support for limited backup files.
v2.4b - 2016-06-05
Corrected bugs.
v2.3b - 2016-06-02
Included debug messages.
v2.2b - 2016-06-02
Corrected bugs. "ERROR:2" should be fixed.
V2.1b - 2016-05-19
Implemented solution from here and here.
V1.9b - 2016-05-04
Implemented solution from here. PLEASE TEST AND REPORT.
V1.8b - 2016-02-04
Corrected bug for Marshmallow.
V1.7b - 2016-02-02
Added support for Marshmallow.
V1.6b - 2016-01-27
Added revert on second run.
V1.5b - 2016-01-26
Corrected bug in check for API version.
V1.4b - 2016-01-26
Changed format of backed up filename.
Added check for API version ( 19<= API <= 22 ).
V1.3b - 2016-01-22
Backed up file is renamed with time and date.
V1.2b - 2016-01-21
Moved code into update-binary.
V1.1b - 2016-01-19
Removed testing commands.
V1.0b - 2016-01-18
Initial submission
XDA:DevDB Information
ExtSD Fix, Tool/Utility for all devices (see above for details)
Contributors
rufus.wilson
Version Information
Status: Testing
Current Beta Version: v2.9b
Beta Release Date: 2016-06-09
Created 2016-01-18
Last Updated 2016-06-15

Tested devices and systems
When you have tested it could you report your experience with the device model and the android version you used.
I will summarize here the success and failures.
Success
OnePlus X - CM 12.1
N4 w/TW 6.0.1 MM
sony z3c concept rom(mm)
Samsung Galaxy Express 2 with CM13
Xperia M with CM13
Sony Z3 .570 stock
asus zenfone 2
Asus ZenFone 4 - Stock v7.4.4 (Lollipop) (all opened apps had FC on reboot)
asus zenfone 5 XOSP rom
Sony Xperia Z3 (Sometimes is overwritten)
SM-G910F Rom ALEXNDR COJ3 Deodexed
Samsung galaxy s5 g900f stock marshmallow
z3c with rom slimm 1.5
Galaxy S7 SM-G930FD 6.0.1 Rooted Xposed
Xiaomi Redmi 1S RR 5.6.8 which is a CM13(R28)
Sony Z3 D6653 running on RXSW Marshmallow Edition [3.0.0] [12/04/16] [6.0.1]
LG L90 D415
Redmi 1s using OctOS M ROM
xt907 JBBL- cm13, 01-05-2016
Redmi 2, CM 13.1-20160417-SNAPSHOT
z3 570 rxsw
LG G3 VS985 variant running CM 13 6.0.1 nightlies. Using 777 Kernel & TWRP 3.0.2
z3 dual d6633 running marshmallow 6.0.1 official
Oppo find 7a x9006 on 6.0.1 rooted with twrp 3.0
Failure
LG D855 32 Gb with CM13 2016-05-10 and TWRP 3.0.0.0 recovery
Sony z3 MM
g900f blisspop 6.01
Samsung N7105T, unofficial wilson3q cm 13

Reserved

not work with my device
zenfone 4
here is my recovery log

hiimpig1 said:
not work with my device
zenfone 4
here is my recovery log
Click to expand...
Click to collapse
Thank you for coming back to me.
Do you have CWM recovery or TWRP?

rufus.wilson said:
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
Click to expand...
Click to collapse
im using twrp 2.8.7.0

hiimpig1 said:
im using twrp 2.8.7.0
Click to expand...
Click to collapse
I have uploaded a new version. Could you test that one?

rufus.wilson said:
I have uploaded a new version. Could you test that one?
Click to expand...
Click to collapse
i flashed, after that all my apps got FC
but its worked

I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)

hiimpig1 said:
i flashed, after that all my apps got FC
but its worked
Click to expand...
Click to collapse
Was a reboot enough to solve the problem?

phoberus said:
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
Click to expand...
Click to collapse
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
chmod 0644 platform.xml

rufus.wilson said:
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
Click to expand...
Click to collapse
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)

rufus.wilson said:
Was a reboot enough to solve the problem?
Click to expand...
Click to collapse
no its not

phoberus said:
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
Click to expand...
Click to collapse
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml

hiimpig1 said:
no its not
Click to expand...
Click to collapse
Can it be a permission problem? Look here.

rufus.wilson said:
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
Click to expand...
Click to collapse
Didn't work for me, but I have a backup :good:

phoberus said:
Didn't work for me, but I have a backup :good:
Click to expand...
Click to collapse
Which version of android do you use?

hiimpig1 said:
no its not
Click to expand...
Click to collapse
Which ROM are you using?

rufus.wilson said:
Which ROM are you using?
Click to expand...
Click to collapse
im using stock rom 7.4.4 from asus

hiimpig1 said:
im using stock rom 7.4.4 from asus
Click to expand...
Click to collapse
Do you still have the FC?

[MOD][Magisk][Universal] A simple init.d enabler v2.2 (system-less)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
I noticed that old init.d enabling methodes aren't working anymore with latest firmwares on the Xperia Z5
I tried many of available traditional methodes (that relies on init.qcom.post_boot.sh, install-recovery.sh ... I believe they stopped working because a lot of them used SuperSU ), also tried many magisk init.d emulators but none of them worked as well. My mod uses simpler and modern method I thought I'd share it with you to help those who still have troubles activating init.d especially newbies
What is init.d ?
Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks..
Click to expand...
Click to collapse
Compability
Code:
- Any device
- Tested with Magisk v14 but should work on all V12+
Bugs
Code:
- You tell me
Downloads
Second post
Credits
@topjohnwu for making this possible
RXSMB Team
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2017-09-27
Created 2017-09-23
Last Updated 2017-07-29

[MOD][Magisk][Universal] A simple init.d enabler (system-less) [Fixed*]
Downloads
Please use remover before updating to new versions
Make sure you read the notes above carefully before downloading !
Magisk 14+
https://www.androidfilehost.com/?fid=962021903579480972
Magisk 15+
https://drive.google.com/open?id=1bzT5Uu2jIZDJpcaBvSMYqF11M-YYz5SJ
Remover UPDATED 27.09.2017
https://www.androidfilehost.com/?fid=889964283620753913
How to make sure it's working ?
Code:
- Go to [B]/data/[/B] if you find the file [B]"initd_test.log" then congrats it's working [/B]
Changelog
Code:
2.2 | 29/09/2017
- Bug fixes for some devices
2.1 | 27/09/2017
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
2.0 | 24/09/2017
- Changed permissions from 777 to 755 (standard)
- Added writing permissions to init.d folder too
1.0 | 23/09/2017
- First release
​
DO NOT STEAL MY WORK!!
FEEL FREE TO USE MY MOD IN YOUR ROM, JUST GIVE PROPER CREDITS !

Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....

Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.

whalesplaho said:
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Click to expand...
Click to collapse
colorado48 said:
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
Click to expand...
Click to collapse
Please update to new fixed version I updated the link now for second time nothing hardcoded it's working perfectly for me on 32.4.A.0.160 should do same for all roms/devices
Do not forget to use remover before updating .. enjoy

New version works now ?
Fingerprint works now too.

I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......

colorado48 said:
New version works now
Fingerprint works now too.
Click to expand...
Click to collapse
good bro enjoy
whalesplaho said:
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
Click to expand...
Click to collapse
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/

korom42 said:
good bro enjoy
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
Click to expand...
Click to collapse
Im on crdroid lineage os and using stock kernel too brov.. 30secs? Okay will try again.

New version is up ! .. minor changes but better update
2.1 | 27/09/2017
Code:
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)

Bro @korom42 there is no initd_test.log in the data folder on my XZ
Verstuurd vanaf mijn F8331 met Tapatalk

This works but breaks both safetynet checks for me on a Z3C LOS 14.1 with Universal safetynet fix 10.1.

@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil

@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil

Adil Tariq said:
[MENTION=5033594]
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Click to expand...
Click to collapse
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.

Adil Tariq said:
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
Click to expand...
Click to collapse
Adil Tariq said:
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Click to expand...
Click to collapse
Alright, if you managed to use the mod while keeping SafetyNet bypass working than that's great
but I won't change anything since it's not a reliable way because the user will have to move his files each time adding new scripts
- for deleting the 00test file did you try a different file manager .. root browser works fine here
Infy_AsiX said:
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Click to expand...
Click to collapse
- Just disable the module from Magisk Manager whenever you need SafetyNet bypass back .. will try to make it SafetyNet compatible in next versions if possible

@korom42 i just want to report that safety is now also broken on my Xperia Z5 Premium E6833 Stock Rom (LOL) after just 2 reboots. Uninstalling this module fixes the issue. Hope you will find a way to make this module work with safetynet....

@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
As for safety net, there is the very easy way to fix it. Just reinstall busybox version 27.2 after each reboot that will return safetynet back to pass state. I use meefik and that helps.
Click to expand...
Click to collapse
Download the app here
Altenative by Stephen (Stericson)

korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
Great! it's working!
Thanks!

korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
crisout said:
Great! it's working!
Thanks!
Click to expand...
Click to collapse
Did you find out another fix to safetynet? It's not working anymore