Database Users

[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?)?

[HOWTO][LP][Xposed]Xposed framework on YotaPhone 2 LP

NOTE:
This post is/was only relevant for users of the original modded stock recovery for YP2. For the newer & better TWRP recovery for YotaPhone 2 installing unsigned packages such as Xposed framework is not an issue.
Please note that the Xposed version below is outdated, Xposed alpha 4 is available. See Xposed for Lollipop thread.
Old post content:
Not exactly a proper development thread, but posting it here anyway because of the relation with the modded recovery, ad the slightly technical angle.
Xposed framework for Lollipop allows you to install modules that tweak/change many aspects of Android. It's pretty powerful as it can hook into existing software and change it's functionality. The version referred to in this post is an alpha version.
Therefore:
Warning: I recommend you don't install this unless you're a nerd. It's not yet stable, and may cause trouble (such as boot-loops).
Also: by the time you read this there may be newer versions, so read the Xposed thread for updates.
Background
The modded recovery image allows to install software signed by either Yota Devices (such as ota update zips) or signed with testkeys, but it does not allow to flash UNsigned zips. Many flashable zips are signed with testkeys (like SuperSU) but rovo89's Xposed flashable zip for LP in the current 20150430 version are unsigned, so we can't flash them as-is.
Flashing it anyway:
There's two ways: the harder and slightly educational way (useful for e.g. when new Xposed versions are released) and the lazy but convenient way.
1) Signing the Xposed framework zip yourself:
You need:
- signapk.jar plus test key and certificate
Get SignApk.jar from somewhere (build it from AOSP source, or download a zip from this thread (I used zipaligner 1.2, linux). This zip contains other stuff, but we need testkey.pk8, testkey.x509.pem and signapk.jar
- Xposed framework zip for LP 5.0 (xposed-sdk21-arm-20150430.zip) from the official thread from here
- java environment (JDK or JRE)
To sign the file put all files in one dir (including xposed-sdk21-arm-20150430.zip) and run:
Code:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 xposed-sdk21-arm-20150430.zip xposed-sdk21-arm-20150430_signed.zip
You just created xposed-sdk21-arm-20150430_signed.zip that you can flash.
2) Using a pre-Signed zipfile:
I attached a testkey-signed version of rovo89's file xposed-sdk21-arm-20150430.zip to this post for convenience, so you can skip the steps above.
Steps to install the Xposed framework for LP
1) put device in fastboot/download mode and boot the modded recovery image (see recovery thread)
2) choose "apply update from ADB" from recovery menu
Code:
adb sideload <yourpath>/xposed-sdk21-arm-20150430_signed.zip
3) reboot
4) choose allow 'unknown sources' in settings->security
5) copy the file XposedInstaller_3.0-alpha2.apk to your phone (or scan the QR code on the Xposed page to download this file to your phone directly.
6) use a file manager (like ES File Explorer, or the built-in Cabinet) to browse to and open XposedInstaller_3.0-alpha2.apk and install it.
Now you can download Xposed modules through the Xposed Installer app. I tried GravityBox [LP] (make sure you select the right version!) to change the launcher grid to 5x5 instead of 4x4. After a reboot that worked. I'm not saying that using GravityBox is safe, they warn that it may cause trouble with non-standard ROM's (such as ours).
Please not that I can't/won't provide any support for Xposed itself, please see the relevant Xposed threads for that.
Credits:
rovo89, author of the Xposed Framework

nice one, many thanks

Does anyone have then latest version please that's signed for this device
Sent from my YD201 using Tapatalk

read the start topic good, every thing you need is in there with links

Gojira-r32 said:
read the start topic good, every thing you need is in there with links
Click to expand...
Click to collapse
Which version of xposed is for yotaphone I see a few different versions on the xposed thread. Link From the op
Sent from my YD201 using Tapatalk

I used xposed-v68-sdk21-arm.zip just two days ago, and signed it myself according to the instructions.
It seems to play well, at least for two days
I just booted TWRP and sideloaded it, I never flashed the TWRP.
Had a little mess getting the driver to install in windows, when TWRP sideloads, it had a new identity in the device manager and I was unable to make accept the drivers I had. So I made a little manual edit in the .inf file from the yotaphone flashtool package, and then was able to load the driver needed. Google was my friend, but I can paste the change here later if someone want it.

Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk

adamo86 said:
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.

No issues with xposed here either. Running alpha4 I believe.

Installed but not active.. That's what i get! Why is thaT?

Thanks!

I signed the last version of xposed using the method in the first post, and flashed (file attached) using TWRP. no issues so far.
no need to say, make sure you backup first!

Bootloop
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?

Wanderess said:
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Click to expand...
Click to collapse
SOLVED. Stock rom (4.4.3 HK) flashed with Yota Flasher. After this everything went smoothly.

Oficial Xposed running with no problems, well just one named Lollipop
Jeopardy said:
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
Click to expand...
Click to collapse
The same with me, Lollipop because using the EPD is so much better, otherwise I would happily be on KitKat, battery life on Lollipop is awfull, I also have the Xposed installed the official one with no problems, running some Modules to prevent battery from draining as much as possible in this Google Sucking Lollipop...

Xposed for Fire HD 8 (6th) 2016

Edit: confirmed method from post #4 worked
Now we have root, time for xposed.
I tried flash xposed framework zip with FireFlash, it stuck at blank screen.
I tried xposed installer, it said wrong platform.
Any other ideas?

2ig2ag said:
Now we have root, time for xposed.
I tried flash xposed framework zip with FireFlash, it stuck at blank screen.
I tried xposed installer, it said wrong platform.
Any other ideas?
Click to expand...
Click to collapse
I'm new to android, can't help
sit and wait

I have been trying to get xposed working since I acquired root. I believe there is a mismatch between the processor and installed os. The CPU identifies itself as a 64-bit (aarch64) but there is no app_process64 in this OS. I tried touching the file and running the installer but that just soft bricked my tablet. Looking at the spec sheet it seems this CPU does not support 64-bit. The normal 32-bit Arm installer gave me the same results. May be time to ask @rovo89 for some advice.

I have managed to get Xposed working on my Kindle. I will lay out the steps I followed. I used the installer from this thread: https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. I installed the "exposed-v87-sdk22-arm64" framework. At this point I received an error about /system/bin/app_process64 being missing. This will be important later. I restarted the tablet and ended up at the Fire boot screen. I plugged the tablet into my computer and tried to adb. I was able to adb and su. I went into /system/bin/ to see what was amiss based on the previous error. I noticed Xposed created a couple files ending with "_xposed" in this directory. I also noticed I had a file named "app_process64_xposed" in this directory. This is when the previous error clicked. I never had a file named "app_process64" on my tablet. The installer should not have created this file.
I fixed this error by running these commands in adb:
1. 'su'
2. 'mount -w -o remount /system'
3. 'rm /system/bin/app_process64_xposed'
4. 'reboot'
Crossed my fingers and waited for tablet to reboot. Got the typical updating system partition screen and waited 10 mins. Xposed was activated and working. Success.
Hope this helps some of you get this working. I would suggest deleting the "app_process64_xposed" file after you run the Xposed installer but before you reboot.

can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送

How you guys rooted it ? on 5.3.2.1 - I yet to get the root. Please guide.

phpbb88 said:
can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送
Click to expand...
Click to collapse
Its a framework that allows people to change their android rom to have features it normally wouldn't. Kinda like cydia on ios

phpbb88 said:
can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送
Click to expand...
Click to collapse
It's when you walk up to a really cute girl and you flash/expose yourself to her and run away.
Exposed framework is like an underlying interface to tweak just about everything in the android UI. It's behavior. Things like the battery, or order in the status bar, etc etc.
* and a lot...LOT more

nbc12 said:
Its a framework that allows people to change their android rom to have features it normally wouldn't. Kinda like cydia on ios
Click to expand...
Click to collapse
smokejumper76 said:
It's when you walk up to a really cute girl and you flash/expose yourself to her and run away.
Exposed framework is like an underlying interface to tweak just about everything in the android UI. It's behavior. Things like the battery, or order in the status bar, etc etc.
* and a lot...LOT more
Click to expand...
Click to collapse
I understood immediately when @nbc12 said its like cydia on iOS. lol
Thanks!

phpbb88 said:
I understood immediately when @nbc12 said its like cydia on iOS. lol
Thanks!
Click to expand...
Click to collapse
right on, yeah you should def. install it and play with it. I haven't yet on this device, but it is very very cool.

smokejumper76 said:
right on, yeah you should def. install it and play with it. I haven't yet on this device, but it is very very cool.
Click to expand...
Click to collapse
will try when I have time to play with my device
but I expect Custom ROMs on fire hd the most important

coltxL2717 said:
I have managed to get Xposed working on my Kindle. I will lay out the steps I followed. I used the installer from this thread: https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. I installed the "exposed-v87-sdk22-arm64" framework. At this point I received an error about /system/bin/app_process64 being missing. This will be important later. I restarted the tablet and ended up at the Fire boot screen. I plugged the tablet into my computer and tried to adb. I was able to adb and su. I went into /system/bin/ to see what was amiss based on the previous error. I noticed Xposed created a couple files ending with "_xposed" in this directory. I also noticed I had a file named "app_process64_xposed" in this directory. This is when the previous error clicked. I never had a file named "app_process64" on my tablet. The installer should not have created this file.
I fixed this error by running these commands in adb:
1. 'su'
2. 'mount -w -o remount /system'
3. 'rm /system/bin/app_process64_xposed'
4. 'reboot'
Crossed my fingers and waited for tablet to reboot. Got the typical updating system partition screen and waited 10 mins. Xposed was activated and working. Success.
Hope this helps some of you get this working. I would suggest deleting the "app_process64_xposed" file after you run the Xposed installer but before you reboot.
Click to expand...
Click to collapse
i have the same problem but when i try to mount system i get permission denied, system is read only, although im rooted cant mount system?? any help appreciated

ahac85 said:
i have the same problem but when i try to mount system i get permission denied, system is read only, although im rooted cant mount system?? any help appreciated
Click to expand...
Click to collapse
did the shell change from $ to # after you typed 'su'?
if not, have you grant access to adb shell?
Code:
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ #

phpbb88 said:
did the shell change from $ to # after you typed 'su'?
if not, have you grant access to adb shell?
Click to expand...
Click to collapse
Hi i had to use kingoroot pc for root access again then the above commands worked. Even though i was fully rooted and had SuperSu installed.
Edit: I think I may have changed SuperSu permissions to "prompt" instead of "grant", which is why it was being denied?
Anyway its all working... Sucess!!

ahac85 said:
Hi i had to use kingoroot pc for root access again then the above commands worked. Even though i was fully rooted and had SuperSu installed.
Edit: I think I may have changed SuperSu permissions to "prompt" instead of "grant", which is why it was being denied?
Anyway its all working... Sucess!!
Click to expand...
Click to collapse
Glad you got it worked out.

@coltxL2717 which version of the xposed installer did you use?
I downloaded the dvdandroid_26_11_1 and fail to install

@phpbb88, that is the installer I used. The script will error but the framework is still being installed.

coltxL2717 said:
@phpbb88, that is the installer I used. The script will error but the framework is still being installed.
Click to expand...
Click to collapse
I cannot install that apk by using file explorer, keep telling me installation failed....
edit: its working now, thanks!

I had the same issue as @ahac85. The kingoroot method he mentioned worked for me as well. You guys find any good/cool xposed modules that worked?

I was wondering if I changed my supersu gettings from grant to prompt would mess anything up? So far I haven't touched it, but would like the normal pop-up prompt that happens when su is requested. And if it doesn't work, that is just weird.

Magiks on Moto Z play

I managed to have magisk and magiskhide working sucessfully, with some manual tricks and workarounds
There is a bug in f2fs that prevents /data/magisk.img to me mounted writable, so the tweek is just moving that file to the /cache partition, which is ext4 and creating a symlink to the original file.
So the steps for a working magisk is.
- Unlock your bootloader
- Install Twrp
- Flash magisk without mounting data partition and boot once.
- Reboot to recovery and open terminal (advanced)
- move magisk.img to /cache partition, changing name ( example: mv /data/magisk.img /cache/magisk_2.img)
- Create a symlink between_files ( ln -s /cache/magisk_2.img /data/magisk.img)
Would be nice if anybody can try to reproduce.

Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.

lpchaim said:
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
Click to expand...
Click to collapse
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.

jblancoperez said:
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
Click to expand...
Click to collapse
Right. I think I'll try this out today and see how things turn out. As for SafetyNet, I though the unlocked bootloader alone was enough reason for it not to work, is this only for some models?
Update: So, @jblancoperez, I've reproduced your steps and Magisk Manager tells me it's installed but root isn't activated and it doesn't let me do anything else as a result.

Things to have a look,
Please confirm in the terminal if /magisk is mounted.
Go back to TWRP terminal and also confirm if the symlink is OK.
Nice to get the output from /cache/magisk.log
It took me a while to have everything right, doing it on TWRP is not the easiest places to move things around.

So, an update. Your method just wouldn't work for me at all, no matter how many times I tried. What worked was following the first part only, as in unmounting data and then flashing Magisk afterwards. I've tried Xposed and Viper4Android; they worked, but both did have to be flashed through twrp as opposed to Magisk Manager, which would throw an error. Not sure if that's on them or on this particular method. I should mention though that SafetyNet wouldn't pass even before xposed and with the hiding settings, not sure why.

You may want to try the kernel where the f2fs bug is fixed, which may be the cause when Magisk hide is not working which would cause Safetynet to fail.

Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?

tag68 said:
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
Click to expand...
Click to collapse
I got bootloop when I install magiks 11.0.

Do you have a logfile of that action in /cache or /cache/recovery which we could show in the Magisk thread?

I was able to upgrade the 10.2 installation.
Will try a new clean installation on the weekend with the f2fs fixed kernel.
I think I got why my procedure is not working for other people. Please try to copy the image instead of moving with the flags preserving de selinux attributes.

jblancoperez said:
Please try to copy the image instead of moving with the flags preserving de selinux attributes.
Click to expand...
Click to collapse
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.

tag68 said:
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
Click to expand...
Click to collapse
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.

jblancoperez said:
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
Click to expand...
Click to collapse
cp -a tries to copy attributes including timestamps. But it only succeeds if you are currently running as root.

xposed framework for huawei p10 lite?

Recently it has come out xposed framework by rovo89 for android N:
https://forum.xda-developers.com/showthread.php?t=3034811
Has anyone tried it on the p10 lite, with rom stock + recovery + root? or in some other device huawei with rom stock and emui 6?
Thanks in advance.

I've tried it and it works fine, but since I rooted my p10 and installed xposed my battery started to drain noticeably faster, so I went back to stock.

I use xposed with magisk v14 and no battery drain(I think)

Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d

mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/du.d
Click to expand...
Click to collapse
I get this too, but to fix I just untick all enabled modules in xposed, reboot, enable modules again and reboot again.

hayabusa2yk said:
I use xposed with magisk v14 and no battery drain(I think)
Click to expand...
Click to collapse
How did you install magisk?

plerohero said:
How did you install magisk?
Click to expand...
Click to collapse
Just flash in TWRP
sorry for my bad English

mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
Click to expand...
Click to collapse
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks

mzeeshan2 said:
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
Click to expand...
Click to collapse
Change permisions for .sh file, chmod 777 to script, reboot and enjoy.
No problems for my.