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

Status
Not open for further replies.
Search This thread
By:
Advanced…
jonboyuk

jonboyuk

Senior Member
May 24, 2007
1,031
139
South West UK
Hi all, I have a quick question regarding this framework.

As with most things on XDA, a nandroid backup is suggested first. However, I'm using a Note 3 and I've just used towelroot to root it, specifically because it doesn't trigger KNOX. As such I cannot change the kernel/rom etc, and can't use CWM etc so can't make a nandroid back up.

Is it risky me installing this framework then the Wanam modules from Play? Ie if I get stuck in a bootloop, I can't just restore Android....any thoughts? :)
 
Maxr1998

Maxr1998

Recognized Developer
Apr 15, 2013
2,151
3,216
24
Germany
maxr1998.de
Google Nexus 4
Nexus 7
jonboyuk said:
Hi all, I have a quick question regarding this framework.

As with most things on XDA, a nandroid backup is suggested first. However, I'm using a Note 3 and I've just used towelroot to root it, specifically because it doesn't trigger KNOX. As such I cannot change the kernel/rom etc, and can't use CWM etc so can't make a nandroid back up.

Is it risky me installing this framework then the Wanam modules from Play? Ie if I get stuck in a bootloop, I can't just restore Android....any thoughts? :)
Click to expand...
Click to collapse
Xposed has a safemode integrated if you get stuck in bootloop.
rovo89 said:
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
Click to expand...
Click to collapse
But of course you always have to remember it's risky to do sth without a nadroid... Anyway, I'd risk it.. [emoji106]

Sent using my nexus⁴ running Mahdi 2.6 with Xposed and hells-Core B47 KK
 
  • Like
Reactions: jonboyuk
egingell

egingell

Senior Member
Apr 10, 2012
4,754
2,059
45
blog.sophielabuf.com
jonboyuk said:
Hi all, I have a quick question regarding this framework.

As with most things on XDA, a nandroid backup is suggested first. However, I'm using a Note 3 and I've just used towelroot to root it, specifically because it doesn't trigger KNOX. As such I cannot change the kernel/rom etc, and can't use CWM etc so can't make a nandroid back up.

Is it risky me installing this framework then the Wanam modules from Play? Ie if I get stuck in a bootloop, I can't just restore Android....any thoughts? :)
Click to expand...
Click to collapse
Everything you do to your phone is risky.

That said, Xposed won't hard-brick your phone.

As for backups, just use something other than nandroid to back it up - I use Titanium Backup. And Xposed has a recovery mode similar to Safe Mode on a Windows PC and accessed in much the same manner.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
 
  • Like
Reactions: jonboyuk
Tungstwenty

Tungstwenty

Senior Member
Nov 1, 2011
1,830
4,512
jonboyuk said:
Hi all, I have a quick question regarding this framework.

As with most things on XDA, a nandroid backup is suggested first. However, I'm using a Note 3 and I've just used towelroot to root it, specifically because it doesn't trigger KNOX. As such I cannot change the kernel/rom etc, and can't use CWM etc so can't make a nandroid back up.

Is it risky me installing this framework then the Wanam modules from Play? Ie if I get stuck in a bootloop, I can't just restore Android....any thoughts? :)
Click to expand...
Click to collapse
If you can reflash only the /system partition, without wiping /data, you'll be able to revert the changes made by the installer (it replaces /system/bin/app_process) and return it to a bootable state without Xposed (or root).
 
  • Like
Reactions: jonboyuk
jonboyuk

jonboyuk

Senior Member
May 24, 2007
1,031
139
South West UK
Maxr1998 said:
Xposed has a safemode integrated if you get stuck in bootloop.

But of course you always have to remember it's risky to do sth without a nadroid... Anyway, I'd risk it.. [emoji106]
Click to expand...
Click to collapse

Done!!! :)

egingell said:
Everything you do to your phone is risky.

That said, Xposed won't hard-brick your phone.

As for backups, just use something other than nandroid to back it up - I use Titanium Backup. And Xposed has a recovery mode similar to Safe Mode on a Windows PC and accessed in much the same manner.
Click to expand...
Click to collapse

Good idea, I use TB, but it just meant that I couldn't restore from a CWM environment. Nonetheless, thanks, I will try the suggested module.

Tungstwenty said:
If you can reflash only the /system partition, without wiping /data, you'll be able to revert the changes made by the installer (it replaces /system/bin/app_process) and return it to a bootable state without Xposed (or root).
Click to expand...
Click to collapse

Phew, as long as I can't create a hard brick as a result, I'm going to risk it!

Thanks you three.
 
cadarn07

cadarn07

Senior Member
Jul 10, 2012
470
432
jonboyuk said:
Hi all, I have a quick question regarding this framework.

As with most things on XDA, a nandroid backup is suggested first. However, I'm using a Note 3 and I've just used towelroot to root it, specifically because it doesn't trigger KNOX. As such I cannot change the kernel/rom etc, and can't use CWM etc so can't make a nandroid back up.

Is it risky me installing this framework then the Wanam modules from Play? Ie if I get stuck in a bootloop, I can't just restore Android....any thoughts? :)
Click to expand...
Click to collapse

Personally, if I didn't have the option to install a custom recovery and backup, etc, I wouldn't mess with too many things like this. That being said, I haven't read about too many bootloops from the framework or modules but anything is possible once you start playing around in /system.
 
  • Like
Reactions: jonboyuk
egingell

egingell

Senior Member
Apr 10, 2012
4,754
2,059
45
blog.sophielabuf.com
mmcneil said:
@ rovo89, I want to add Xposed to my custom build android build; based the response show above, do I include only the Xposed folder or do I need to add all three folders that are found under the "Source code" listing in the OP ? Thanks.

Mike
Click to expand...
Click to collapse
I see only one folder. Where are you looking?

Edit: Oh, I see what you're referring to.

I don't know much about ROM compiling, but I've seen apps included in the ROM (e.g. SuperSU including its binary) with their original signatures intact. Why does it need to be compiled with the ROM? Can't it just be dropped into the system/app and system/bin folders respectively in the zip file?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
 
Last edited:
mmcneil

mmcneil

Senior Member
Mar 8, 2009
262
65
OnePlus 7 Pro
Google Pixel 4 XL
egingell said:
I see only one folder. Where are you looking?

Edit: Oh, I see what you're referring to.

I don't know much about ROM compiling, but I've seen apps included in the ROM (e.g. SuperSU including its binary) with their original signatures intact. Why does it need to be compiled with the ROM? Can't it just be dropped into the system/app and system/bin folders respectively in the zip file?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse

Thanks for responding. In answer to your question, I'd like to have it listed in "Settings" as opposed to just showing up as an icon in the app drawer. So for example, if I had a section in Settings called "MyTools", I'd want to have Xposed show up in that section. I don't know that I could do that with just the .apk I hope I explained that properly :eek:

Thanks,

Mike
 
H

HaYaHa

Senior Member
Oct 29, 2012
117
10
Yesterday my phone crashed. Now gravitybox isn't working anymore. If I try to open gravitybox it says: "Gravitybox system framework now responding. Exiting." So I tried to remove the framework and gravitybox and install it again, but it didn't solve the problem.

Does somebody know how to solve this problem? And I am asking this question in this tread because it is about the framework. If it is the wrong tread you can recall me.
 
egingell

egingell

Senior Member
Apr 10, 2012
4,754
2,059
45
blog.sophielabuf.com
HaYaHa said:
Yesterday my phone crashed. Now gravitybox isn't working anymore. If I try to open gravitybox it says: "Gravitybox system framework now responding. Exiting." So I tried to remove the framework and gravitybox and install it again, but it didn't solve the problem.

Does somebody know how to solve this problem? And I am asking this question in this tread because it is about the framework. If it is the wrong tread you can recall me.
Click to expand...
Click to collapse
You might try finding the right thread. Hint: This ain't it.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
 
  • Like
Reactions: HaYaHa
C3C076

C3C076

Inactive Recognized Contributor
Dec 15, 2012
7,749
24,726
Bratislava
ceco.sk.eu.org
HaYaHa said:
Yesterday my phone crashed. Now gravitybox isn't working anymore. If I try to open gravitybox it says: "Gravitybox system framework now responding. Exiting." So I tried to remove the framework and gravitybox and install it again, but it didn't solve the problem.

Does somebody know how to solve this problem? And I am asking this question in this tread because it is about the framework. If it is the wrong tread you can recall me.
Click to expand...
Click to collapse

This message means that the module was not loaded by xposed framework for some reason.
Double-check your framework installation plus make sure module is installed in phone's internal memory (not on sd card or other external storage) and that it is activated in xposed installer.
 
  • Like
Reactions: HaYaHa and r1m
remixkilla

remixkilla

Senior Member
Apr 2, 2011
338
63
I deleted the xposed uninstall zip. How do i get it back?

Sent from my Nexus 5 using XDA Premium 4 mobile app
 
theknut

theknut

Senior Member
May 4, 2009
990
4,148
www.theknut.de
Last edited:
F

fozzie

Senior Member
Aug 28, 2006
1,083
573
theknut said:
It doesn't sound necessary to re-install Xposed (by reinstall I mean Xposed Installer -> Framework -> Install/Upate) but it might be the faster way instead of downloading and copy & pasting the zip file.
Click to expand...
Click to collapse
Well of course reinstalling the framework isn't going to help. It's the app that needs reinstalling.
 
Status
Not open for further replies.

Similar threads

rovo89
  • Locked
  • Sticky
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
Replies
49
Views
7M
rovo89
rovo89
rovo89
[DISCUSSION] Xposed for Lollipop
Replies
13K
Views
4M
B
breversa
romracer
[UNOFFICIAL] Systemless Xposed for Android 5.1/6.0 - v86.1 / 20160928 / SDK22/SDK23
Replies
7K
Views
3M
D
Deleted member 11604687
T
[2019.5.1][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27)
Replies
8K
Views
3M
C
CookieCream
wanam
  • Locked
[UNOFFICIAL][5.1/6][v87.1][28 Nov]Xposed for Samsung Lollipop/Marshmallow
Replies
6K
Views
2M
wanam
wanam

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 638
    rovo89
    rovo89
    Xposed 2.4 beta1/beta2

    This is Xposed version 2.4 beta1. The main new features and fixes in this version are:
    • Support for Android 4.4 (KitKat)
    • Significant performance improvements of the framework
    • Viewer for the debug.log in the installer
    • Check in the installer whether Xposed is actually active and working

    First of all, I would like to thank the 45 people who donated to get me a Nexus 5, from a little "thanks" to huge amounts of money. I was really impressed and hope you like this update.

    In detail:
    Xposed should now fully support KitKat. As mentioned, that wouldn't have been possible at this time without your support.
    Modules should continue to work if they don't rely on AOSP internals that have changed in KitKat. One example: It seems that the battery icon is no longer an (animated) image, but a Java implementation. Obviously, any modules that try to replace the battery image will no longer work. The Xposed framework can't do anything here, the module needs to be rewritten. Therefore, if some of your modules don't work, please get in contact with the module author first. You will probably see an error in the new debug.log viewer in this case.
    Xposed isn't compatible with ART, I can't say yet whether it will be in the future (will require a major rewrite if possible at all). As you would get into a bootloop if you try to combine Xposed+ART, Xposed automatically resets the choice to "Dalvik". If you want to test ART, you must uninstall the framework.

    The performance improvements apply to the very core of Xposed, the method hooks, in all Android versions. In a test app developed by @exidler, the overhead per call used to be ~71 μs (= 0.071 ms) per call to a hooked method (with one empty callback handler) on my Galaxy S2. Now it's ~13 μs (= 0.013 ms). That's a relative improvement of factor ~5.5x. Thanks to @exidler for the research and several suggestions! I have sent a pre-beta to @kamso, who had reported lags with older versions. Now everything works fine for him. Anyway, I wouldn't say that Xposed had bad performance before. Keep in mind that we are talking about significantly less than a millisecond here.

    The debug.log viewer should give a quick impression whether Xposed and modules could be loaded fine. It also includes options to save the log to SD card (so it's easier to transfer it to a PC etc.) and send it via mail.

    The Xposed Installer now checks whether the latest version of the framework is active. If not (e.g. because it's not installed yet, you forgot to reboot or something in Xposed doesn't work), you will see a warning in the welcome screen and at the top of the module list.

    Finally, there were some other minor improvements and fixes and new/updated translations.


    Developers:
    As a reminder, please keep the debug.log clean. It's only helpful if it's not as spammed as logcat. You should only use XposedBridge.log() for error messages and other unexpected situations. If everything runs fine, it shouldn't write anything to the log. If you really need to keep some logging in published builds, please use either logcat or make it an opt-in options (i.e. disabled by default and the user enables it if he runs into problems).

    Apart from that, there was a little API change: https://github.com/rovo89/XposedBridge/commit/3c18f6f6bd4e0ec57898b3b3a79b5584d0396054
    I assume that very few modules use the "extra" field to transfer information between beforeHookedMethod() and afterHookedMethod(). If you do, simply replace it by getExtra().

    Layout inflation hooks now also work if the layout has been included in other layouts. That's actually a pretty tricky use-case for the "extra" parameter mentioned about (and other tricky technologies).

    If for some reason you need to determine the active XposedBridge version in your module, you can use XposedBridge.XPOSED_BRIDGE_VERSION.

    findMethodBestMatch() now also looks for protected and package-private methods in superclasses. That's mainly useful if you use the callMethod() or callStaticMethod() helper.

    UPDATE: (beta2)
    The new beta should fix the "read-only filesystem" errors. If you used to experience them, please try this version. Otherwise, there is no need (and no advantage) to update.

    UPDATE:
    The final version is out, please use it instead (see first post / in-app installer).
    View
    479
    rovo89
    rovo89
    The ART of patience

    Regarding ART possibly becoming the default runtime engine: I think that's good news because it means that we will get a stable version of ART then. I'm reluctant to work further on ART support at the moment for mainly three reasons:

    1. Time. I used to spend every evening and every weekend for Xposed, either to give support here (often answering the same questions again and again), writing code or researching about bugs or new ideas. As you may have noticed, there are now days or even weeks where I don't even log on to XDA, and I'm actually glad about this.

    2. Experimental software is bound to contain bugs, even severe ones. There is a reason why Google didn't make this choice available for the typical user (and keep in mind, we are not typical users). I neither want people to blame Xposed if their phone starts acting up nor do I want to hunt bugs which are caused by a runtime engine that is explicitely labelled as not finished yet.

    3. As long as ART is experimental, it's much easier to make big changes to the code. Once a final version is out and used by the masses, quality engineers we be much more careful not to break things. That means that Xposed for ART on 4.5 (or whatever it will be called) might need to be completely different than for ART on 4.4. More variants means more time for maintenance. And I don't feel like pushing something out now just to drop support again in a later version. There is not enough benefit of using ART at the moment to justify that.

    You know, I had already worked on ART support and spent several dozens of hours reading the code, looking for ways to hijack it, implementing my ideas, doing trial and error and starting again from the beginning. I finally had my Nexus 5 boot with Xposed in early December and quickly tested the App Settings module. I'm happy about that, but I also know that this was just a very experimental version, less ready than ART itself. It is totally hacked together and only tested with the stock ROM. ART is quite complex and has several different modes. It's not worth giving the current development to someone else before I have tested these things on my phone, where I can debug much better than instructing someone else to do it. It also requires rewriting app_process to be a light executable again, which loads either the Dalvik or ART Xposed library, depending on your settings. That would require changes in the installer as well, etc. etc.

    So you see, there is still lots of work to do. At the moment, I'm not actively working on it, but trying to get some other things fixed (e.g. LG ROMs) or improved (installation via recovery, better installation feedback in case root access failed, static Busybox package). And as I said, I do have other things in my life as well. It's not about money, that's what I have my full-time job for. I work on Xposed for fun (and maybe a bit for the reputation ;)), so the best way to ensure that I keep on working on it is not taking away the fun part of it. Don't pressure me like it was my duty to implement something ASAP (!!!), be patient even if it takes a bit longer until I answer and join the volunteers who help answering basic questions here so I don't have to. Thanks!
    View
    315
    rovo89
    rovo89
    General information on Xposed has been moved to this thread: http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
    The FAQ has been moved to this thread: http://forum.xda-developers.com/xposed/-t2735540
    Questions, suggestions, bug reports and so on can be posted in the Xposed General forum (for the installer/framework/development only) and in the Xposed Framework modules forum (for anything module-related).
    View
    222
    osm0sis
    osm0sis
    Xposed Framework Installer (Flashable Zip)

    Announcement: Xposed Framework v2.5+ comes with an option to flash its own install zip via recovery, making my package obsolete. I'll leave them up for posterity; could be useful should the need arise for downgrading on some devices. Cheers all! 10000 downloads is pretty cool. :)

    Xposed Framework v2.2+ has fixed JB4.3 installation and v2.4+ has added support for KK4.4, but for those that still want it, or cannot install via the APK due to /system write protection like HTC's S-ON, here is an updated zip frontend method for installing the framework; now for Xposed Framework v2.4.1.

    You MUST have the Xposed Installer APK installed FIRST. The zip will detect if you do not and stop.

    Flash this in recovery and my frontend script (the update-binary) will detect the correct architecture and SDK version to use the appropriate Xposed app_process and busybox builds (x86, armv5, v6 and v7 & sdk 15 and 16+ supported), and should detect the uid of the Xposed Installer APK on-the-fly and set up the required files with it.

    It leaves a log behind in /data/local/tmp/xposed-log.txt either way with more details about how it went. :cool:

    It also unpacks Xposed-Disabler-Recovery.zip to /sdcard/ (or /sdcard/0/ if it exists) to be as close to the APK install method as possible. For those wanting another method to reactivate after a ROM update or toggle Xposed disabled/enabled, @amishxda has also created a cool "Xposed toggler" zip here.

    Note: Xposed Framework files and the install.sh used are the work of @rovo89 and @Tungstwenty; I have only created a recovery flashable zip to function as an alternative frontend for the framework installation process. I take no credit for their fantastic work.


    P.S. If you found this handy then please check out my Odds and Ends thread for more flashable goodness. :D

    5351 downloads of v2.1.4 when removed. 1049 downloads of v2.2 when removed.
    View
    193
    rovo89
    rovo89
    Xposed 2.5 final

    This is Xposed version 2.5 (final). The main new features and fixes in this version are:
    • Rewritten framework installation/uninstallation
      • Uses interactive su (via libsuperuser) to provide improved compatibility with different Superuser apps
      • Better feedback when root access fails (doesn't freeze the app anymore)
      • Offers installation via custom recovery (CWM/TWRP), either flashing the file automatically or manually
    • Safemode to disable Xposed with hardware keys to get out of (most) bootloops
    • Compatibility with Sony/LG ROMs (4.3 and 4.4), Meizu ROMs (4.4)
    • Debug setting to disable resource hooking as a temporary workaround for incompatibilities with some theming engines (not all modules can be used in this mode)
    There are also other improvements and fixes, especially many translations updates.
    In case you get a message "Segmentation fault" during installation, you can now download an additional app which provides statically compiled versions of BusyBox (a lot bigger, but should work with every ROM). It's not needed otherwise.

    Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.

    As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.
    View

New posts