Xposed - Legacy thread. Don't panic, Xposed is still here.

[lklun]

This means test command fails. Run this command in adb shell:

/system/bin/sh -c "test -f /data/xposed/app_process"; echo $?

let me know what number it shows.

If number is not 0 (zero) then it means something is wrong with shell / test command or its not been allowed to run. (or adb in PAC rom is not running as super user)

Running that command while booted in the rom looks like this:

[email protected]:/ # /system/bin/sh -c "test -f /data/xposed/app_process"; echo $?
a/xposed/app_process"; echo $? <
0

And in TWRP:

~ # ←[6n/system/bin/sh -c "test -f /data/xposed/app_process"; echo $?
/system/bin/sh -c "test -f /data/xposed/app_process"; echo $?
CANNOT LINK EXECUTABLE: cannot locate symbol "__memmove_chk" referenced by "/sys
tem/bin/sh"...
1

Except for the error message, please note the "1" that was returned in recovery

As far as I know the # indicates running as root, right? It is present in recovey, even though the "~ # ←[6n"-part looks a little strange to me. Typing "su" in adb shell in recovery just returns "/sbin/sh: su: not found"

So you mean that I just copy /data/xposed/app_process to /system/bin/app_process and change file permissions?

In that case you can manually backup app_process (of PAC rom) first and then copy app_process (of Xposed). It should enable Xposed.

 

[formeriphoneuser]

Will there likely be any problems with installing this to PAC ROM?

 

[SecUpwN]

Will there likely be any problems with installing this to PAC ROM?

NO.

 

[cleverior.ipul]

could you paste the content of /data/xposed/debug.log ?

now i can open ur xposed and install framework but i cant download module.

 

[formeriphoneuser]

NO.

Thx! So I can also assume no problems with codefireXperiment ROM, yes?

 

[liudongmiao]

now i can open ur xposed and install framework but i cant download module.

everything seems ok.
there is almost no modules for gb, so download function is useless.
however, you can download xprivacy module manually.

 

[amishxda]

And in TWRP:

CANNOT LINK EXECUTABLE: cannot locate symbol "__memmove_chk" referenced by "/sys
tem/bin/sh

Except for the error message, please note the "1" that was returned in recovery

As far as I know the # indicates running as root, right? It is present in recovey, even though the "~ # ←[6n"-part looks a little strange to me. Typing "su" in adb shell in recovery just returns "/sbin/sh: su: not found"

Cannot locate symbol means linking is failing. Installation is not proper or its TWRP bug. Please report to TWRP.

So you mean that I just copy /data/xposed/app_process to /system/bin/app_process and change file permissions?

Yes. Make sure to copy original app_process as app_process.orig first.

 

[rovo89]

Cannot locate symbol means linking is failing. Installation is not proper or its TWRP bug. Please report to TWRP.

Just one idea: Maybe /sbin/sh works better, because it's part of the recovery, not of the ROM. @lklun could you try this as well?

 

[amishxda]

Just one idea: Maybe /sbin/sh works better, because it's part of the recovery, not of the ROM. @lklun could you try this as well?

Yes makes sense, updated my script to use /sbin/sh instead of /system/bin/sh

Tested using CWM, may be people using TWRP ( @lklun ) can also report.

Here:
http://forum.xda-developers.com/showpost.php?p=45188739

 

[SecUpwN]

Thx! So I can also assume no problems with codefireXperiment ROM, yes?

YES.

 

[lklun]

Just one idea: Maybe /sbin/sh works better, because it's part of the recovery, not of the ROM. @lklun could you try this as well?

Yes makes sense, updated my script to use /sbin/sh instead of /system/bin/sh

Tested using CWM, may be people using TWRP ( @lklun ) can also report.

Here:
http://forum.xda-developers.com/showpost.php?p=45188739

Running "/sbin/sh -c "test -f /data/xposed/app_process"; echo $?" in TWRP returns 0:

~ # ←[6n/sbin/sh -c "test -f /data/xposed/app_process"; echo $?
/sbin/sh -c "test -f /data/xposed/app_process"; echo $?
0

Flashing the toggle in TWRP works fine. However, I ended up in a bootloop like I always do, which I usually resolve by formatting /system, flashing the rom, booting it and installing Xposed through the Xposed installer. However, this is exactly what I'd like not to have to do. I would be so much smoother just to flash the toggle I'm just going to describe what happens. My phone is encrypted with the built-in encryption in Android. Therefore, my normal boot procedure looks like this:

1. Bootanimation showing
2. Enter SIM-pin
3. Enter password to decrypt storage
4. Bootanimation starts all over again and phone boots

After flashing the toggle (or using backup scripts in addon.d) the procedure looks lite this:

1. Bootanimation showing
2. Enter SIM-pin
3. Enter password to decrypt storage
4. Bootanimation starts all over again and eventually the "Optimising apps"-sign shows up
5. When optimising apps is finished, the "Starting app"-sign is shown
6. Bootanimation starts all over again and the phone is unable to boot into the rom

After "Starting apps" is shown, the phone should go directly into the rom. After flashing the toggle, it does not, however. Exactly the same happens if I use the backup scripts provided in the first posts of the thread.

I guess this is rom related, but it seems so strange to me that just using a custom app_process during the first boot after a rom update causes a bootloop. Would you guys like a logcat @rovo89 and @amishxda and if so, with what contents?

 

[amishxda]

Running "/sbin/sh -c "test -f /data/xposed/app_process"; echo $?" in TWRP returns 0:

Flashing the toggle in TWRP works fine. However, I ended up in a bootloop like I always do,

I guess this is rom related, but it seems so strange to me that just using a custom app_process during the first boot after a rom update causes a bootloop. Would you guys like a logcat @rovo89 and @amishxda and if so, with what contents?

Umm, I do not think this is related to toggle flash. It simply copies Xposed app_process.

Not sure if there is something special required in case of an encrypted storage.

 

[rovo89]

I guess this is rom related, but it seems so strange to me that just using a custom app_process during the first boot after a rom update causes a bootloop. Would you guys like a logcat @rovo89 and @amishxda and if so, with what contents?

Yes, please. I can have a look at it. Just to be sure: If you install Xposed via the installer after flashing the ROM, everything works fine?

 

[Oberth]

Well done and a big thumbs up.

Well done rovo89. I have test this on my Novo 8 and it ran so that's a start. have you looked at any of the other plugins as yet. The dpi changer would be a huge bonus for GB based tablets

 

[abalam]

Wow man what an app. Did not know this was possible on stock, unbelievable! Away from CM and back on stock

 

[iammodo]

Set this up today on my RAZR I and it works just fine.
RAZR I x86
Stock rooted ROM
Cwm touch recovery.


Sent from my Nexus 7 using XDA Premium 4 mobile app

 

[dk_zero-cool]

@rovo89

Was thinking, would it be possible to get the 'MethodHookParam.method' extended to include things like TypeParameters and such like regular Method objects? The availability of the method name itself is not very useful without the rest of the information as classes can have multiple methods with the same name. At least have the types that was requested in findAndHookMethod() parsed along, those are already available to XPosed anyways.

 

[lklun]

Yes, please. I can have a look at it. Just to be sure: If you install Xposed via the installer after flashing the ROM, everything works fine?

Yes, if I boot the phone without Xposed after flashing a rom and then install it via Xposed Installer everything is fine: no problems booting and the modules I use work the way they should. Thus, it seems I have to boot once without Xposed for some reason.

I'm not a developer myself so I don't know very much about logcats, but I suppose I should filter it in some way? If so, how? Or should I just run "adb logcat" and send you the output?

 

[rovo89]

@rovo89

Was thinking, would it be possible to get the 'MethodHookParam.method' extended to include things like TypeParameters and such like regular Method objects? The availability of the method name itself is not very useful without the rest of the information as classes can have multiple methods with the same name. At least have the types that was requested in findAndHookMethod() parsed along, those are already available to XPosed anyways.

Just cast param.method to Method and you have all this information. The type is Member because you can also hook constructors and Constructor doesn't inherit from Method.

Yes, if I boot the phone without Xposed after flashing a rom and then install it via Xposed Installer everything is fine: no problems booting and the modules I use work the way they should. Thus, it seems I have to boot once without Xposed for some reason.

I'm not a developer myself so I don't know very much about logcats, but I suppose I should filter it in some way? If so, how? Or should I just run "adb logcat" and send you the output?

Yes, just send the whole log. If you are afraid it could contain sensitive information, feel free to send me a link via PM.

 

[dk_zero-cool]

Just cast param.method to Method and you have all this information. The type is Member because you can also hook constructors and Constructor doesn't inherit from Method.

Well I'll be damned, thanks
Should have posted here before I made my work-around, now I will have to redo it :crying: