Hello, I have problems installing Xposed on my Samsung Galaxy Tab 2 7.0, Android versión 4.0.3 unrooted with cwm Philz Touch 6 versión 6.0.4.6.
I have tried installing it in the classical way and it says the latest version of xposed is currently not active.
I have tried installing it in the Recovery Automatically and it keep saying the latest version of xposed is currently not active, I managed to make that message dissapear if I make a soft reboot antes installing but antes I reboot normally it goles back to the same message.
And when installing in Recovery Manually it brings an error, it says:
In recovery Mode
Did not find /data/data/de. robv.android.Xposed.installer/bin/app_process
Pleas make sure to press install / update in the xposed installer app before flashing this zip.
E: Error in
data/media/files/Xposed-Installer-Recovery
(Status 1)
Installation aborted .
I would appreciate any help since I am new to the forum and if I posted in the wrong section please move it dont delete it.
i have the same problem trying to install Xposed on my Samsung Galaxy S2 4G (GT-i9210T) Android 4.0.4 ROOTED
1) installing using CLASSICAL - starts install/update then crashes
2) installing using RECOVERY (flash zip automatically) - starts install/update then says...
-copying Xposed-Disabler-Recovery.zip...
-copying Xposed-Installer-Recovery.zip...
-Could not copy Xposed-Installer-Recovery.zip to /cache
3)installing using RECOVERY (write zip to SD card, flash manually) - it starts install/update. Tells me to boot to recovery mode.
When entering recovery mode, It cant find the xposed files to extract and install in the SD card.
Anyone that can help would be greatly appreciated. thanks
Have you checked the FAQ? If that doesn't help, please post a logcat.
GermainZ said:
Have you checked the FAQ? If that doesn't help, please post a logcat.
Click to expand...
Click to collapse
thanks germainZ
i shouldve read the FAQ first. (im a noob)
I installed XposedInstallerStaticBusyBox_v1.apk in my phone then i successfully installed the new framework! AMAZING. :good:
If you didnt tell me to read the FAQ page, i wouldnt have know. UR THE MAN! thank you so much GermainZ
hello,
I once installed xposed on LG G3 via recovery before the updated version.
it was working, but only when i changed to permissive.
now with the updated xposed, when i try to install from the app itsef it says my phone not compatible.
"Xposed is not (yet) compatible with android SDK version 21 or your preccessor architecture (armeabi - v7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by "/data/data/de.robv.android.xposed.installer/chache/app_proccess"; caused by library "libdvm.so" not found"
i saw other writing about their d855.. it means the problem is on my phone?
anybody had this issue too?
also i cant remove xposed, says it cant find a backup.
thanks !
I am by no means an expert so the following is only related from my experience,no warranty is implied or given, but this was the first rom I have flashed etc and I only did it last night
Once I put lollipop on to my phone as per this post xposed would not install via the app itself after reading the various threads I found this
[OFFICIAL] Xposed for Lollipop followed the instructions and xposed was installed.
Not sure if I went wrong somewhere but this threw up an issue with lgquickcover not working , some more reading found this booted to recovery using the power/volume key method and flashed the zip from here and the issue was resolved
I think it is worth mentioning xposed is only at alpha at the moment and as such some modules ( in particular g3tweaks I miss it ) do not work
working here. (lg g3, d855, blisspop v2.1 with selinux status already set to permissive)
xposed should say
Xposed on LG G3 D855 - error armeabi and libdvm.so - update ?
hi there,
any update regard this ?
I'm able to install / uninstall the "Xposed install" app but, cant get it install/update due to those errors:
Xposed is not (yet) compatible with android SDK version 21 or your preccessor architecture (armeabi - v7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by "/data/data/de.robv.android.xposed.installer/chache/app_proccess"; caused by library "libdvm.so" not found"
a[[_process - 58
xposedbridge.jar - 54
Phone is root
Android 5.0
core 3.4.0
V20h-ISR-XX
is there a workaround or something ?
i had similar problems on my g3 (d855) on lollipop, then i tried this:
http://forum.xda-developers.com/lg-g3/development/tool-installer-xposedlg-g3unofficial-t3094514
and problem solved. good luck !!!
tnx, working process... still have some problems
when pressing install I'm getting a black screen and an error
"Parse error, failed to mount sd card (unknown error 150) and failed to map file. installation aborted."
attached picture
when rebooting system, I have the xposed app installed but not working, asking for restart, but noting happen after soft or hard rest.
ludstr said:
when pressing install I'm getting a black screen and an error
"Parse error, failed to mount sd card (unknown error 150) and failed to map file. installation aborted."
attached picture
when rebooting system, I have the xposed app installed but not working, asking for restart, but noting happen after soft or hard rest.
Click to expand...
Click to collapse
as i can see in the picture you are using CWM. I did it with TWRP. you can try....
hi @ludstr and @rhystagram
i found another solution. you need to install xposed for lollipop 5.1 instead of xposed 5.0. here is the link: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Hi , I once flashed xposed in my g3/D855 stock rom and get cover error so I renamed lgcover.apk in twrp recovery and problem solved , now I changed my rom into cm12.1 and NOT instaled xposed , is there any way that I can make my smart cover work again ? if not would restoring to stock rom make the cover work again or ... ?
ludstr said:
when pressing install I'm getting a black screen and an error
"Parse error, failed to mount sd card (unknown error 150) and failed to map file. installation aborted."
attached picture
when rebooting system, I have the xposed app installed but not working, asking for restart, but noting happen after soft or hard rest.
Click to expand...
Click to collapse
As I can see you don't have a custom recovery, like TWRP, first you need to do is root "if your phone is rooted then skip this" then download an app called "Flashify" then go to this thread and download the latest TWRP and make sure it is unziped, http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
then open Flashify, Grant for root access, then select flash recovery and then select the recovery boot.img file and flash it after that you should be OK.
then try and flash the xposed framework zip and you should be good to go
hope this helped you
PS see this before flashing xposed
http://forum.xda-developers.com/lg-g3/general/how-to-xposed-running-properly-stock-t3030261
Hello,
Im pretty new to this kind of stuff. So forgive me. I've Nexus 4 device, and got tired of mobile radio active bug.
Android verions 5.1.1
Looked everywhere for the fix and cried on gogole bug report page.
Now i found information about this xposed module, and mobile radio active fix on this forum.
Ive rooted my device. (confirmed with root checker app)
I had custom recovery: clockworkmod recovery v6.0.4.7 (later switched to openrecovery-twrp-2.8.5.2-mako to test and stayed on it )
From this page http://forum.xda-developers.com/showthread.php?t=3034811
i have installed XposedInstaller_3.0_alpha4.apk
App requires (red text) to flash the package, so i am putting this .zip (xposed-v75-sdk22-x86.zip) on my device and trying to flash it through recovery.
chosing it, process starts, and ill write you everything it says
(that is clockworkmod recovery log)
-- Installing /sdcard/0/xposed-v75-sdk22-x86.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /data/media/0/xposed-v75-sdk22-x86.zip
(Status 255)
Installation aborted
tried many times, redownloading the file, renaming it to a.zip
same message every time.
I have also switched to
openrecovery-twrp-2.8.5.2-mako
Tried to flash it using this.
Also error:
updating partition details...
.. done
Full SELinux support is present
MTP Enabled
Installing '/sdcard/xposed-v75-sdk22-x86.zip'...
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
E: Error executing updater binary in zip " /sdcard/xposed-v75-sdk22-x86.zip'
Error flashing zip ' /sdcard/xposed-v75-sdk22-x86.zip'
Updating partition details...
... done
Comment below box "FAILED" (red color)
clicked wipe cache/dalvik
reflashed and getting same error
Am i doing something wrong? Ive no idea what to do, whats the problem. Or maybe some of you had same issue and figured out how to deal with it?
Any answer appreciated.
Thank you.
~~~~~~~~~~~~~~
Out of topic question:
Does Cyanogenmod have this mobile radio active fixed? I'd just switch to it if theres no way installing xposed on my nexus 4 with stock adroid)
The Nexus 4 has an ARM processor, and you're trying to flash the zip for an x86 processor. The flash is failing in order to stop you from putting the wrong software on there.
Try again with the xposed-v75-sdk22-arm.zip file. This was explained repeatedly in the first two posts of the official discussion thread.
I can see now where i've done it wrong after re-reading that post knowing what you just told me.
Must've been some weird article about nexus 4 and its processor that led me to think my processor is 32bit and i thought its ok to use x86 file even tho it says ARM everywhere. And trusted it more over the chart in the main discussion topic.
Everything comes down to my lack of knowledge.
Thank you for your patience and help.
flashed ARM file and it worked perfectly
Topic to be closed.
Thanks again!
Good evening from Spain.
I tried to flash Magisk onto my SM-J530F (Samsung Galaxy J5 2017) but not successfully.
Here's the log:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs.
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Consider that I did the following:
- Flashed stock rom (J530FXXU2ARB3_J530FPHE2ARB3_PHE.zip content)
- Flashed "CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f.tar" in Download mode via Odin, to root and install SuperSU, since it's needed
for flashing TWRP to avoid any bootloop.
- Flashed TWRP.
- Since I already have TWRP, I tried to uninstall SuperSU from the very app, in Options > Full unroot but gave "Uninstallation error", so then I tried to uninstall SuperSU by flashing "UPDATE-unSU.zip" on TWRP.
- Once that is done, I tried to flash "Magisk-v16.0.zip" and it throwed the log I've above mentioned.
- Since it says: "! Boot image patched by other programs.
! Please restore stock boot image", I rebooted it onto Download Mode, and flashed ONLY the BL (bootloader/boot) slot. Came back to TWRP, I flashed again "Magisk-v16.0.zip" but still have the same problem.
Hope there's any solution to install Magisk onto my SM-J530F. Thank you.
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Well, something changed!!!
The problem related with the boot image is solved but I still have the " Failed to mount '/system' "
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Thank you very much.
EDIT: Despite this problem: "Failed to mount '/system' (Device or resource busy)", your solution was correct! Now I have Magisk correctly installed.
Thank you
Nice to hear it worked. Just for the record, the "Failed to mount /system" message is a TWRP thingy. The Magisk installation is done at the "-Done" line.
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
saoudien07 said:
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
Click to expand...
Click to collapse
Provide a recovery log or it's going to be impossible to say what the issue is...
Didgeridoohan said:
Provide a recovery log or it's going to be impossible to say what the issue is...
Click to expand...
Click to collapse
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
saoudien07 said:
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
Click to expand...
Click to collapse
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Didgeridoohan said:
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Click to expand...
Click to collapse
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
saoudien07 said:
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
Click to expand...
Click to collapse
That would work, but you should be able to open it directly with pretty much any text editor as well. If you're going to post the log text directly, please at least use HIDE tags...
So here what I just did:
I wanted to do a last try to get that error 1 msg and get the repport directly to publicate it here...
So I decide to go to a clean basis. So,
1- Install all the stock ROM with odin. I choose the Home_CSC
Was another just CSC without Home, dont know exactly which one I had to choose, I choose Home_CSC.
2- Turn the fone off
3- Turn it back to download mode
4- Install the TWRP recovery, and I did not reboot.
5- Turn off the fone.
6- Turn on to recovery mode.
7- Format the data (yes)
8- Reboot to Recovery mode.
9- Install Magisk!
AT MY BIG SURPRISE I DID NOT GET ANY ERROR MSG!!! The installation finished without error!
So I continued...
10- install No verity
11- install SuperUS 2.82
13- Reboot the phone.
I was thinking that the root was ok, now I have a new pb. When I tryed to verify with Root Checker, it says no root. When I entered the app, it said BINARY OCCUPIED.
So any suggestion?
saoudien07 said:
9- Install Magisk!
...
11- install SuperUS 2.82
Click to expand...
Click to collapse
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
Can I put a link to the tuto here??
For you guys to have a lock at it?
saoudien07 said:
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Can I put a link to the tuto here??
For you guys to have a lock at it?
Click to expand...
Click to collapse
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Didgeridoohan said:
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Click to expand...
Click to collapse
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
saoudien07 said:
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
Click to expand...
Click to collapse
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Didgeridoohan said:
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Click to expand...
Click to collapse
Thx you one more time. Going to install some of my app and configure my new fone then do a backup, for a clean restoration in some months...
I have a problem for the Backup with TWRP. When I want to do a Backup, I get this msg:
failed to mount /data (Invalid argument)
I ve looked on google to fix it, the solution I found is to change data to ext2, then back to ext4.
The pb is that it is removing everything from my phone?
Anyone is having the same issue??
Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Hi, i am rooting samsung a5 a520w. I am following the steps in the instructions (https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535).
Now I met a problem like this:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v17.1.zip'
I have no idea where is the boot.img located. All documents in the external card is:
RMM-State_Bypass;
no-verity-opt-encrypt-6.0;
Magisk_17.1
@imcn001 Your answer is in the link from the post you quoted.