[UNOFFICIAL][5.1/6][v87.1][28 Nov]Xposed for Samsung Lollipop/Marshmallow

Status
Not open for further replies.
Search This thread

phrotac

Senior Member
Mar 8, 2009
1,303
1,084
51
Fort Smith, AR
I don't have that luxury,I have an S7 edge so i can't have TWRP

---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------



When i flashed with flashfire, i had a systemui force close
Are you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.

Sent from my SM-N910T3 using Tapatalk
 

Ibuprophen

Senior Member
Sep 4, 2012
9,545
6,494
Upstate New York
Are you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.

Sent from my SM-N910T3 using Tapatalk

This is only True when it comes to devices that are not rooted.

If the device is properly rooted, then this statement is false.

I don't have that luxury,I have an S7 edge so i can't have TWRP

---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------



When i flashed with flashfire, i had a systemui force close

If your S7 Edge is properly rooted, i would recommend installing BusyBox (if you haven't already done so).

In addition, have you looked at the following thread that applies to the rooting and XPosed installation (amongst other things) of the S7 Edge while keeping the Stock ROM?

GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Galaxy S7 or S7 Edge by psouza4

Good Luck and Happy New Year!

Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
 
Last edited:
  • Like
Reactions: phrotac

Lmax579

Senior Member
Mar 28, 2013
1,338
139
Waukegan, IL
This is only True when it comes to devices that are not rooted.

If the device is properly rooted, then this statement is false.



If your S7 Edge is properly rooted, i would recommend installing BusyBox (if you haven't already done so).

In addition, have you looked at the following thread that applies to the rooting and XPosed installation (amongst other things) of the S7 Edge while keeping the Stock ROM?

GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Galaxy S7 or S7 Edge by psouza4

Good Luck and Happy New Year!

Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).

Thank you, and happy new years to you as well.... Im properly rooted but I'm on a custom rom
 

grep_i

Senior Member
Sep 19, 2015
1,551
621
Are you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.

Sent from my SM-N910T3 using Tapatalk

You know you are in the thread of Xposed for Samsung devices, this version is not intended to bootloop on stock Samsung rom (TouchWiz), it is just optimized for it.
Therefore your claim is not true.

---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------

I don't have that luxury,I have an S7 edge so i can't have TWRP

---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------



When i flashed with flashfire, i had a systemui force close

Can you be a little more specific does the systemui force close happen before, during or after flashing ?
Have you also tried clearing dalvik/cache ?
Is it only systemui that force closes or are there more processes or apps that force closes ?
Can you provide some log file of force close in the form of logcat ?
 

Lmax579

Senior Member
Mar 28, 2013
1,338
139
Waukegan, IL
You know you are in the thread of Xposed for Samsung devices, this version is not intended to bootloop on stock Samsung rom (TouchWiz), it is just optimized for it.
Therefore your claim is not true.

---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------



Can you be a little more specific does the systemui force close happen before, during or after flashing ?
Have you also tried clearing dalvik/cache ?
Is it only systemui that force closes or are there more processes or apps that force closes ?
Can you provide some log file of force close in the form of logcat ?

Don't know how to do it, the logcat,once I unlock the phone,the system fc. I'm gonna try to wipe Dalvik and cache this time

---------- Post added at 08:47 PM ---------- Previous post was at 08:09 PM ----------

Don't know how to do it, the logcat,once I unlock the phone,the system fc. I'm gonna try to wipe Dalvik and cache this time

It worked after I wiped Dalvik & Cache... Is there a way to have the nav bar from Gravity box without having a systemui fc?
 
  • Like
Reactions: grep_i

grep_i

Senior Member
Sep 19, 2015
1,551
621
Don't know how to do it, the logcat,once I unlock the phone,the system fc. I'm gonna try to wipe Dalvik and cache this time

---------- Post added at 08:47 PM ---------- Previous post was at 08:09 PM ----------



It worked after I wiped Dalvik & Cache... Is there a way to have the nav bar from Gravity box without having a systemui fc?

Don't know about that but I know Gravitybox is an app that can cause problems with custom roms and/or Xposed as they are already heavily modified.
 

phrotac

Senior Member
Mar 8, 2009
1,303
1,084
51
Fort Smith, AR
Are you running a stock rom? I only ask becsuse installing Xposed on a stock Samsung rom will bootloop it. If you are stock, flashing the uninstaller should fix it.

This is only True when it comes to devices that are not rooted.

If the device is properly rooted, then this statement is false.
Good to know. Thank you very much :)






Sent from my SM-N910T3 using Tapatalk

---------- Post added at 04:17 PM ---------- Previous post was at 03:59 PM ----------

You know you are in the thread of Xposed for Samsung devices, this version is not intended to bootloop on stock Samsung rom (TouchWiz), it is just optimized for it.
Therefore your claim is not true.

---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------



Can you be a little more specific does the systemui force close happen before, during or after flashing ?
Have you also tried clearing dalvik/cache ?
Is it only systemui that force closes or are there more processes or apps that force closes ?
Can you provide some log file of force close in the form of logcat ?
My apologies. I thought I was in the Official rovo89 thread and was only repeating what I read:
rovo89 said:
Known issues:
- Bootloops on Samsung stock ROMs.
That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
So, am I right to assume that this thread is one of the "work arounds" rovo89 was referring to?

Again, my apologies :)

Sent from my SM-N910T3 using Tapatalk
 
Last edited:

grep_i

Senior Member
Sep 19, 2015
1,551
621
Good to know. Thank you very much :)






Sent from my SM-N910T3 using Tapatalk

---------- Post added at 04:17 PM ---------- Previous post was at 03:59 PM ----------


My apologies. I thought I was in the Official rovo89 thread and was only repeating what I read:

So, am I right to assume that this thread is one of the "work arounds" rovo89 was referring to?

Again, my apologies :)

Sent from my SM-N910T3 using Tapatalk
It's OK and yes as I already mentioned and as stated in the OP this version is optimized for Samsung devices.:good:
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 1533
    Disclaimer

    Your warranty is now void.
    You are using my files at your own RISK.
    I am not responsible for any bricked devices.


    This is an Xposed framework variant built and tested against the Galaxy S7 (G930F), but it should support all other Samsung devices (GS5, Note 4/5, GS6E, GS6E+...) running TW Android 5.1.1 and 6.0.

    Xposed was made and still maintained by @rovo89, so please make sure you give all the credits to him for making our device better.

    Samsung made a lot of changes to ART without providing the sources, that's why it took a while to workaround some of their changes, more information here.

    It supports Stock and close to stock Roms.

    This unofficial Xposed version does NOT break support for any other device supported by official Xposed, which means it still support all devices supported by the official one, this version adds Samsung and XZ compressed odexes support.

    Prerequisite:
    - Stock (Odexed and Deodexed) 5.1/6.0 Roms
    - CWM recovery


    Bugs report:
    - If you get any lag, broken feature or any App force closing, post your Xposed logs.
    - If you get a boot-loop, reboot and get the logcat with "adb logcat" as soon as it gets detected on your PC (you may need to use a Linux distribution to get earlier logs).

    I will not reply to any bug reports that ignore the above notes, explain clearly your issue so i can help you, i can't read your mind.

    Versions names:
    • ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)
    • ARM64 means the devices that are running arm64 operating system (Galaxy S7/S6, Note5 and all their variants...)
    • SDK22 means Android Lollipop 5.1.x
    • SDK23 means Android Marshmallow 6.0.x

    How to install:
    - Install Xposed installer app attached here.
    - Make a nandroid backup
    - Copy the Xposed file and the uninstaller to your sdcard
    - Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
    - Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.

    Download.

    Mirror.

    Sources:
    https://github.com/wanam/Xposed
    https://github.com/wanam/android_art
    https://github.com/wanam/XposedBridge
    https://github.com/wanam/XposedTools
    https://github.com/wanam/xz-embedded

    Donate to @rovo89
    All credits go to @rovo89 for his amazing work on xposed framework
    Thanks to @_riddle for his work on oat2dex
    Thanks to @romracer @arter97, @clark44, @insty, @svadev , @jthrasher47 and @imfaraz for making it possible to port Xposed to Samsung devices.
    Without these people, this would not have been possible at all.
    469
    Changeslog:

    v87.1(28/11/2016):
    - This update fixes a compatibility issue with the new Note5 UX Roms (Technical details).

    v87.0(25/11/2016):
    - This version includes @rovo89's fix to workaround the Google's November security patch that prevents system from booting if some files are still open while forking zygote (including modules on /data/app), more details about this issue can be found here.

    v86.1(04/09/2016):
    - Merged the alternative and the main MM version, the changes we used to apply for some specific Marshmallow TouchWiz are now applied within the main version, thanks to @dkcldark, (technical details).

    v86.0(09/07/2016):
    - More compatiblity with ROMs that use a Resources subclass for e.g. theming, like most Huawei stock ROMs (*)
    - Incorrectly compiled modules are now rejected, the warning which started to appear with v84 is now an error
    - A bit of general cleanup and minor fixes
    More details.

    v85.1(30/05/2016):
    - Add Huawei theming engine support (details).
    - Ensure the recompilation on Huawei EMUI Roms (details).

    v85.0(28/05/2016):
    Updated to the official Xposed v85:

    • Fixed frequent boot freezes, especially with modules that access many files (details)
    • Built-in way to get a full logcat (details)
    • Crashes not related to Xposed/ART are no longer written to the normal Xposed logs
    • On encrypted devices with boot password, the password prompt is now shown quicker
    • Warning for developers to disable "Instant Run" in Android Studio, otherwise the module can't be loaded
    • 6.0 only: Cherry-picked some ART commit included in CyanogenMod and other ROMs
    • 6.0 only: Forced clearing Dalvik cache when upgrading from versions before 85 (would have been necessary for 84 and might have caused some boot loops)
    More details here.

    v84.0(04/05/2016):
    Updated to the official Xposed v84 with support for LG encrypted apps, you can find more details about the changes here.

    v83.0(26/04/2016):
    An alternative version "alt" for some Samsung variants (N910G/P, N915F...) that come with two more native changes, check this branch for more details.
    This variant should be used for Samsung variants (N910G/P, N915F...), and for a non listed device only if the main version does not work, and you should use this alternative version with stock Roms with no modified framework files.

    v83.0(25/04/2016):

    Cumulative update improving some devices support (Huawei and HTC), it fixes also some bugs related to some new aosp changes, more details here and here.

    v81.0(12/04/2016):
    Updated API to the official Xposed 81.0, this update brings XZ compression to MM builds, unfortunately Samsung still uses this compression type for its Apps odexes (Thanks to @dkcldark for the hint).
    I also included few other changes from LL to prevent boot-loop on some older devices that will get MM, we cannot trust Samsung on this, they should learn from Google/CM some basic rules about how manage their devices branches, the framework differences should not be major between different devices running the same Android version.

    The Sprint Note 4 MM builds are not supported yet (an example of the major changes I'm talking about), a test version is available, test it and provide a logcat if it still boot-loops.

    v80.1(02/04/2016):
    This MM update reverts an aosp wip change, this should fix some apps like Yandex maps.
    No update required for LL Roms.

    v80.0(11/02/2016):
    This is an update to the latest rovo89's changes, i added back the reverted commits, rovo89 fixed the issue related to the apps that uses some apk protection (MyAndroidTools).

    I made a small changes to the bridge to catch an exception on some TW 5.1.1 Roms that may not contain "restoreUnsupportedServices" method.
    I posted also a unified uninstaller for all version.

    v79.1 for Lollipop (20/01/2016):
    - Reverted an aosp commit that is causing crash with some Apps native code, i still have no idea why but i hope rovo89 can figure out what's wrong with this change.
    - Mute failed Samsung hooks, Samsung Lollipop FWs have different mdpp implementation for some devices.
    - Disabled Instrumentation detection on Xposed, we need to keep the native Samsung hooks active even when instrumentation is detected, big thanks to rovo89 for investigating this issue and Enyby for the tests.
    This should fix crash on Game guardian App, My Android tools...

    v79.1 for Marshmallow (19/01/2016):
    - Refactored Samsung security hooks and cleanup some useless hooks for Marshmallow.

    v79.0 for Marshmallow (28/12/2015):
    More details here.

    v79.0 (17/12/2015):
    This is an update to the official Xposed v79, that contains many bugs fixes, more details here.

    v78.1 (09/12/2015):
    This update includes some fixes by @rovo89 that let stock TW Roms boot up correctly with "everything" filter.
    It includes also fixes some secure storage compatibility issues that I managed to reproduce running "everything" filter, i also patched Xposed bridge with a fix for SHealth and Private mode, they are required for any TW user running Xposed, so i prefer to include it on the framework, you don't need to enable it on Wanam Xposed.

    My Xposed version still runs the default "speed" filter for dex2oat, if you want to run "everything" filter to force the compilation of all apps on boot, add bellow lines to your build.prop:
    Code:
    dalvik.vm.dex2oat-filter=everything
    dalvik.vm.image-dex2oat-filter=everything
    I also reverted a change related to a Samsung bug that seems to be fixed on its latest updates, i tested it with full stock G920F-OKX running stock kernel with systemless Root.

    v78.0 (16/11/2015):
    This update includes some back ported changes and bugs fixes that @rovo89 included on Xposed for Android 6, check more details here.

    v75.8 (30/10/2015):
    - This update bypasses Class rejection on some cases where a method fails the verification and causes the whole class to be rejected, and keep logging the compilation errors.

    v75.7 (29/10/2015):
    - The new update fixes a major boot loop issue caused by xposed safe mode, some users do intentionally disable Xposed while booting by hitting the device's hardware keys which create a file "/data/data/de.robv.android.xposed.installer/conf/disabled" that disables some required hooks i implemented to disable Mdpp security checks, and leads to a boot loop because Knox/Mdpp rejects our custom Art libraries, so we disable xposed safe mode for TW Roms, use uninstallers instead.

    v75.1 to v75.6 (26/10/2015):

    - Support XZ compression for all devices (non Samsung included)
    - Fixed a Bridge bug, thanks to @arter97 for the head up
    - Fixed a Samsung packaging bug for arm64 devices

    v75.0 (08/10/2015):

    Updated to @rovo89 latest changes:
    - Unified version to support old Roms and new ones that come with new app_process changes
    - Disabled dex2oat watchdog
    Check here for more details.

    v74 (07/10/2015):
    This update revert "disable must_relocate=false" and avoid the header image checks instead, as it seems the only change on previous version that may cause the random reboots reported by some users.

    I posted also a variant (under android_511_r19 folder) that is compatible with some newest FWs (OI9+ on GS6), these FWs comes with a new security commit introducing a new zygote parameter that breaks Xposed. Do NOT use this variant on older Roms.

    v74 (02/10/2015):

    This update comes with XZ compression support, thanks to @rovo89 for pointing me to xz-embedded.

    It should fix SPlanner, Samsung core apps and few other xz compressed System apps odexes...
    Xposed will takes more time to decompress and recompile those apps, according to my tests, it takes 6 seconds to dexopt compressed S Planner odex with a size of 2.6MB/10MB, Samsung uses this compression type because of its low compression ratio to gain more space for more and more bloats
    http%3A%2F%2Fforum.xda-developers.com%2Fimg.xda-cdn.com%2FpbRevCoW7fotdZjlVDDaJMD7zBs%3D%2Fhttp%253A%252F%252Fforum.xda-developers.com%252Fimg.xda-cdn.com%252FTajnA7KO1o5nDvXdS1BiQxu5b9c%253D%252Fhttp%25253A%25252F%25252Fforum.xda-developers.com%25252Fimg.xda-cdn.com%25252Fq_PZoBMFhMEIvMped5kxF0juUcA%25253D%25252Fhttp%2525253A%2525252F%2525252Fforum.xda-developers.com%2525252Fimg.xda-cdn.com%2525252Frzw0x2viRCJ8E2MNj3_vaXac99c%2525253D%2525252Fhttp%252525253A%252525252F%252525252Fforum.xda-developers.com%252525252Fimg.xda-cdn.com%252525252FRQIE8KA3gRpuJRuFi3XO2PnXjrM%252525253D%252525252Fhttp%25252525253A%25252525252F%25252525252Fforum.xda-developers.com%25252525252Fimg.xda-cdn.com%25252525252Fyt_oSG5PG--3Ey0LEJjbo3j2UuE%25252525253D%25252525252Fhttp%2525252525253A%2525252525252F%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fforum.xda-developers.com%2525252525252Fcdn3.xda-developers.com%2525252525252Fimages%2525252525252Fsmilies%2525252525252Fsmile.gif


    v74 (15/09/2015):
    - This will fix the low space issue on dirty repacked deodexed Roms that may still contains odexed files, this issue was caused by a failed verification of the image header of "boot.art" on TW Roms, somehow one of the offsets "root_image" is wrong, check here for more details.

    We just ignore it for now to let xposed boot-up on odexed Roms and avoid the misleading low space warnings, this does NOT mean stock odexed Roms are supported, i tested it only with my debloated Odexed OH8 Rom for GS6 (G920F), so use it at your own RISK and no need to report any bugs if you run it on a stock FW.

    No space version are provided, use the main on instead.

    v74 (11/09/2015):
    - Updated to official xposed v74
    This update should fix the gms maps module crashe and maybe some other non system apps that generate odex file on the device.
    I reverted back to the default speed dexopt filter for better perfs, for people who are getting a low space, i posted an other version with dexopt space filter, we still don't know the cause of this issue.
    I made an attempt to support odex Roms (included on the new version 11092015), i followed the same idea of @rovo89 used for gz compression support, renamed odex files to force installd to run dex2oat, the Rom boot up, but with the same low space issue that makes it unusable! So no need to try it for now on odexed Roms.

    v73 (03/09/2015):
    - Re-based my build on @rovo89 repos (v73)
    - Fixed the shared prefs bug (thanks to @romracer and @cryptyk)
    - Balanced dexopt filter to save more space on bloated TW Roms, it saves more than 300MB on my debloated Rom so it should do better on bloated ones, if you still get out of system space and apps FC, there is nothing i can do for you, going ahead to save more space will lead on a performance issue, ask your Rom cooker to debloat it.

    v71 (28/08/2015):

    - Support for the Galaxy Note 5
    - Get rid of the modifications on the framework files, i ported all my hacks to the Xposed bridge, and Art libraries
    Big thanks to @rovo89 for his assistance and his patches.
    This build requires stock untouched framework file, if your Rom comes with a modded "core-libart" and "conscrypt", it will boot-loop.

    v71 (22/08/2015):
    - No dexopt filters, this will cause more apps to recompile on the first boot, it will take more boot time but should improve the performances.

    v71-b3 (19/08/2015):
    - Added back some specific certificates checks for Chinese hosts

    v71-b2 (18/08/2015):
    - Fixed FC on Nova and some apps keys.

    v71-b1 (17/08/2015):
    - Initial release
    68
    Awesome work. Thanks :D
    45
    Excellent response. I am honored to be in the presence of a Lineage team member (truly). I've had many problems with Xposed and quit trying to use them in one of my basic ROMs some time ago.

    I am impressed so far with the performance of 14.1. And the space it freed up from all the Sammy stuff on the stock
    I'm looking for good things from your team and have yet to be disappointed. Now I need to break it so I can really get under the hood.

    Great work team,

    I checked rovo89's art changes on L and M branches, i just noticed only few code style changes here, i think it's not worth downloading both sdk22 and sdk23 sources for such build.

    I will stop here and let rovo89 continue his work with Samsung support on Nougat, we are aware there are still few bugs with Samsung Roms, mainly the Knox ASLR feature enabled on some devices, as a temporary workaround you can still disable this feature with "ro.knox.enhance.zygote.aslr=0" on your "/system/build.prop", rovo89 will see if there is a way we could support this feature on xposed.

    That being said, unless there is a security patch that may break L/M xposed support in the future, i will close this thread.
    39
    Xposed for GalaxyS6 Samsung Touchwiz Marshmallow build posted, it's built for arm64 devices only.

    Samsung did it in clean way this time, just a small changes to Art plus the Konx security ones of course.
    I didn't include xz support, it's not required on the current M build, maybe planned for low space devices, i hope they will switch to gz since it's supported on aosp.

    We don't have proper custom recovery that supports the new bootloader, you need to switch to old one to flash this patch, @arter97 already posted how to do that, get the old and new BL here and Odin 3.10.7 here.

    1- Copy Xposed patch and the uninstaller to your sdcard
    2- Reboot to download mode
    3- Flash oldsboot through Odin with Unchecked Auto-Reboot
    4- Reboot again to download mode
    5- Flash TWRP or Philz recovery through Odin with Unchecked Auto-Reboot
    6- Reboot to the recovery and flash Xposed
    7- Reboot to Download mode and flash newsboot through Odin with Checked Auto-Reboot
    Enjoy.

    Thanks again to @rovo89 for his amazing work, and to @arter97 for troubleshooting my git issues.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone