[Q] Error in Installing Xposed Framework in Marshmallow - Xposed General

[Q] Error in Installing Xposed Framework in Marshmallow
I got this error message.
History:
1. recently flash factory image (razor-mob30j-factory-a2878e21.tgz)
2. then flash TWRP (twrp-3.0.2-0-flo.img)
3. flash Elemental X kernel (ElementalX-N7-5.11.zip)
4. root with SuperSU (SuperSU-root-BETA-v2.67.zip)
5. flash Xposed Framework (xposed-v84-sdk23-arm.zip)
got this attached error

Looks like your /system partition is full.

Related

[Q] Fail to flash xposed framework

I downloaded framework and app here but everytime I flash the framework it shows ' error executing updater binary in zip'. However I can flash other zip like kernel. Could someone do me a faver?
Nick Huang said:
I downloaded framework and app here but everytime I flash the framework it shows ' error executing updater binary in zip'. However I can flash other zip like kernel. Could someone do me a faver?
Click to expand...
Click to collapse
I would guess that you need to use an older version of TWRP - the latest builds are a bit ropey.
Same issue here , on BlissPop 3.2 07 May 2015 Version with Blisspop's Stock Kernel and TWRP 2.8.6.0 -_- (For OnePlus One)

[Q] Manual Framework Installation for Recovery Files?

Hey guys,
I recently installed CM11 on my Moto X. Installation went successfully and I installed the Xposed apk. Now when I go to framework it tells me "Installation is only available via recovery". Does anyone have a zip file containing these framework files? thanks in advance.
SOLVED: Installed wrong version of Xposed.

2.7 Boot Loop recovery... Tried everything!

So I made a mistake because I ended up installing xposed on stock Samsung and now I'm stuck in a boot loop.
I installed the framework using the 2.7 experimental1 apk from the xposed.info site.
I've tried a few methods of removing xposed and they've all failed:
Flash the uninstaller zip in custom recovery
Manually create a disabled file at /data/data/de.robv.android.xposed.installer/conf/disabled
Deleted the modules.list file at the same location
Restored app_process.orig to app_process in /system/bin
I can get into custom recovery and I've wiped the dalvik cache and cache as well. What else can I do?
kenhcwoo said:
So I made a mistake because I ended up installing xposed on stock Samsung and now I'm stuck in a boot loop.
I installed the framework using the 2.7 experimental1 apk from the xposed.info site.
I've tried a few methods of removing xposed and they've all failed:
Flash the uninstaller zip in custom recovery
Manually create a disabled file at /data/data/de.robv.android.xposed.installer/conf/disabled
Deleted the modules.list file at the same location
Restored app_process.orig to app_process in /system/bin
I can get into custom recovery and I've wiped the dalvik cache and cache as well. What else can I do?
Click to expand...
Click to collapse
What Android version are you running? Xposed v2.7 is for KitKat (or below) devices only.
You could try to flash the stock ROM of your device or simply restore your nandroid backup (which you should have made before installing Xposed).

Error reinstalling Xposed Framework

Hi everyone!
I have a Meizu M2 note with 5.1. Lollipop. I had xposed framework installed, I upgraded to the new version of flyme, I rooted again the phone, and now I can't install the framework.
In xposed installer (without the framework installed) it says XposedBridge.jar included is 54, and not app_process included (it says --). It seems I don't have the original app_process file in system.
Then, I made a factory reset and I reflashed the original system zip, and I tried again; but I can't install the framework neither.
And when I try to uninstall the framework (because the installer gives me the option), it says: "no backup found in /system/bin/app_process.orig" and "/data/de.robv.android.xposed.installer/cache/busybox-xposed: not found".
What else can I do?
Thanks in advance, and sorry because of my bad English!
For 5.1 (and 5.0 and 6.0) xPosed is very different. Please read fully http://forum.xda-developers.com/showthread.php?t=3034811
You will need to flash xPosed in custom recovery and have alpha installer (from bottom of first post in linked thread)

Magisk Install Error - insufficient Partition Size

Hello. I'm attempting to install magisk on a Samsung Galaxy Tab 4 10.1 (SM-T530NU). Base android has been replaced with crDroid (crDroid-7.1.1-20170312-v2.3).
When I go to flash the magisk .zip via TWRP the log reads:
...
-Flashing new boot image
! Insufficient partition size
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v17.1(17100)'
Updating partition details...
...done.
I have tried the following:
made sure to have the latest zip from Magisk Manager
removed previous partial installs of Magisk by using the flashable remover
unrooted supersu (which I'm also no longer able to flash now, systemless or not, to reestablish root and try other methods--it sticks on the boot screen)
reflashed base crDroid
pulling Magisk 17.3 separately from Manager and using that to flash
I haven't found any resources on whether the 'insufficient partition size' problem is with TWRP or the Magisk flashing process so I haven't found anything to try specifically to fix that.
The last thing I have to try is making the flashable boot image and fastbooting it.
Linked here is an image of the TWRP output: imgur . com/a/CATYid4
Thanks
did you manage to fix this

Categories

Resources