[RESOLVED][RESOLVED][RESOLVED][RESOLVED]
Hi, i have an issue with xposed framework using xposed-v87-sdk23-arm64.zip whereby my phone would enter a bootloop and throw an error on the installer that goes something like this:
mv: cant rename 'system/bin/
app_process' : Device or resource busy
Error 1 occurred
I am on build 32.2.A.0.253
Any help is appreciated. Thanks.
Try update to 305?or into TWRP flash flashable
ah sorry, i rerooted and its resolved
i have given up on xpose installers years ago for xperias! something always goes wrong!
for me the main issue was never the xposed installer itself!
GravityBox with Gem Xperia always make something destructive and I always ended up reflashing stockrom!
Related
for me after flashing this rom it was like everything working perfectly until i tried to install xposed installer i couldnt find it after installed , but showing that , is installed when i checked from setting /app/all , then i download latest one xposed installer 2.4.1 from this page (http://forum.xda-developers.com/showthread.php?t=1574401) past it by root explorer in to : system / app by deleting or replacing old xposed installer which is already installed and reboot it and got xposed installer working fine , i written because i thought may be helpful to you guys who dont know about it like myself initially i didnt know how to solve it but finally luckily happen , thanks guys .
Greetings all..
I am working on the Not e 4 and run a large collection of Xposed mods
I have a Sprint Note 2, Note 3 and Note 4 and the 2&3 have never given me any issues with Xposed Framework Modules.
The frame work
Several are causing boot loops upon reboot.
The device will not boot into safemode- which is a huge pain if you did not do a backup in recovery.
I just wanted to remind everyone that if you install Xposed ( and ignore all of the "make sure you nandroid/ backup first messages) this time REALLY MAKE SURE YOU BACK UP /System at least before you activate mods.
I will post a list of the ones giving me issues shortly as I work out process of elimination.
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
I don't use many xposed modules and don't have boot loop issues with the ones I use. My problem is not all options in Wanam works. Like disabling sound waning when putting the volume too high. Hopefully the Wanam devs will fix that.
gfp11289 said:
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
Click to expand...
Click to collapse
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
xxSTARBUCKSxx said:
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
Click to expand...
Click to collapse
I turned off Software Uodates and it still comes up in the notification bar
I don't get any service either upon installing and restarting with xposed
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Deleted. Thanks. ^^^^^^^^
hermeticist said:
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Click to expand...
Click to collapse
I'll try it when I get home
I just install this in TWRP?
gfp11289 said:
I'll try it when I get home
I just install this in TWRP?
Click to expand...
Click to collapse
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
hermeticist said:
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
Click to expand...
Click to collapse
The thing is that I didn't have any modules on. I just installed it, updated it, rebooted, and I'm stuck with no service until after I uninstall it
Weird
Maybe I could try to flash Xposed in TWRP? If that's even possible..
gfp11289 said:
Maybe I could try to flash Xposed in TWRP? If that's even possible..
Click to expand...
Click to collapse
All you have to do is install the apk. Then once in Xposed, install the framework.
Id try uninstalling the framework, deleting the apk and download a fresh apk of xposed and start fresh. Dont associate TWRP with installing Xposed.
I think its working now. For some reason the update stays on my status bar for awhile before it turns off by itself. I tried to send myself some text messages last night and they took a long time to send, or just never sent at all. I have some decent status by my house so that wasn't an issue. I might've not given my phone enough time to boot up xposed or something, but regardless it's working now.
Being connected to wifi, does in anyway affect sending text messages while I'm on xposed? I barely had enough time to test it out when I was at home but driving around my city I was sending myself text messages and they seemed to go through okay.
Wanam Xposed
11/5/14 Wanam Xposed Module update available.
Drama!!! It is just Xposed Framework.
Got my 5x for Christmas. I immediately unlocked and flashed TWRP, and started playing with ROMs. Once I settled on cyanogenmod, I decided to flash xposed. After flashing it, upon boot I got stuck in a loop of "Unfortunately, NFC service has stopped." errors.
Since then, I have been troubleshooting on the factory image. I formatted everything, even the sdcard, and then flashed the factory image. I then booted, then flashed and booted TWRP.
From this point, I have tried, in every order imaginable, flashing SuperSU (systemless and traditional), flashing xposed, and installing the Xposed Installer apk. No matter what I do, I get the NFC error loop. I have also tried both xposed v78, v79, and v79 dirty flashed over v78.
The only thing which has been even mildly successful has been flashing the original 6.0 factory image and then following the above steps. This results in a working xposed installation, but then upgrading to 6.0.1 and reflashing xposed causes the loop again.
From what I can tell by reading here and on /r/nexus5x, plenty of other people are having this issue, and no one seems to have the actual cause or solution. So please, if you have seen this issue, post the circumstances (be as specific as you can with versions, orders, etc), as well as your personal solutions. And if anyone has the true cause and/or solution please post that as well.
Deleted
gpvecchi said:
Deleted
Click to expand...
Click to collapse
v78 doesn't work for me either. I've seen a number of people mention that v79 causes this error, and that reverting to v78 will fix it. However, I cannot get either v78 or v79 to work.
lpreams said:
v78 doesn't work for me either. I've seen a number of people mention that v79 causes this error, and that reverting to v78 will fix it. However, I cannot get either v78 or v79 to work.
Click to expand...
Click to collapse
I just clean flashed mmb29q, tried to install v80, and got the nfc bootloop. Only way to fix was to flash the xposed uninstaller.
Tried this: checking "Enable su during boot" in the SuperSU app, then reflashing Xposed. No luck.
And nfc was not on prior to flashing xposed the first time.
Xposed v79 worked for me fine on mmb29p.
I used supersu 2.66 on mmb29p, and 2.67 on mmb29q.
Busybox installed?
Disabled NFC in settings first before flashing xposed
I got this too on MMB29Q with NFC enabled in settings. I disabled NFC in settings prior to flashing on the next try and flashing xposed v80 worked fine. After installing xposed framework, I was able to turn on NFC in settings again and all is well.
Go it to work. This was my path: Checked every box in SuperSu Settings tab that wasn't checked (e.g., enable multi-user, enable su during boot, etc.), installed the Xposed apk, flashed Xposed zip in TWRP.
Setup: MMB29Q, TWRP 3.0, SuperSU 2.67
I have the same issue trying to use layers manager. Wonder if it's related
I've installed v77 all the way up to v82, all with the same result while also trying everything mentioned before
UPDATE: I've checked literally everything now, including multi-user (didnt think that was necessary before), everything works now on v80
Sent from my Nexus 5X using XDA-Developers mobile app
Hello guys
I'm experiencing the following issue:
I am trying to install the latest Oxygen OS update on my OP3 (talking about 3.2.8). I can do so and at first it works fine, but as soon as I activate Xposed (not the framework itself, that's no problem at all. It's appearently ANY module that needs to be activated) the booting process doesn't finish and I get stuck on boot-animation-screen. Has anybody experienced the same issue or even found a way to fix it?
Also, the Xposed Uninstaller ZIP doesn't seem to work on the OP3. It failes. And any time I want to try again I need to restore a hole Nandroid. Is that a known (or fixed) issue?
Here's some backround info:
- It's not just my phone, same issue on my sister's
- Root and Xposed framework themselves are no problem. Issue starts when activating any Xposed-module
- Xposed worked flawlessly on previous version
- I tried it several times
Would really appreciate any feedback, even just if it's a known issue!
Thanx
What xposed version are you using?
Use xposed v87 , it will work fine then
Or you can try the systemless xposed.
Hello ! Is there a way to install xposed framework on A7 2017 nougat ?
Using the Magisk module with the Material Design XPSD worked perfectly on my A7(2017)
dudedude420 said:
Hello ! Is there a way to install xposed framework on A7 2017 nougat ?
Click to expand...
Click to collapse
Hello! I've never posted on XDA before but since I spent 6 hours yesterday trying to figure out a proper way to do just that so I might as well help.
This worked perfectly for my A720F/DS but it should also work with any A series nougat device. Notice that the MOST important part for this to work in other devices is choosing the correct xposed SDK according to your android system and CPU. Magisk is universal, no need to worry about download one specific for your device.
I'll start with a short summary in case you know a lot about the topic and then proceed to a step-by-step process.
Only the "systemless" AKA Magisk way works flawlessly, it's pretty simple when using the correct files. If you already have Magisk properly installed all you have to do is download the latest "Material Design Xposed Installer" and have active the 24 SDK module from the Magisk Manager app.
STEP 1
ROOT WITH MAGISK AND USE VERITY PATCH TO AVOID KNOX PROBLEMS
1. Put magisk v14.0 and dm-verity patch onto the sdcard in the phone.
Download the latest magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Verity Patch from here: https://forum.xda-developers.com/samsung-a-series-2017/help/how-to-install-magisk-v12-0-root-enable-t3611527 You might need this link later to use S Health...
2. Flash TWRP using Odin - You cand download both here https://forum.xda-developers.com/samsung-a-series-2017/development/xcc-t3591448
Important Note for Installing TWRP on A7 2017: Disable auto-reboot in Odin so that after flashing TWRP it says PASSED but instead of rebooting and Knox un-doing what you just did, you will now attempt to go to download mode again (Vol Down + Home + Power Button) but as soon as the screen goes black (meaning the phone is off) you will instead go to Recovery mode, simply pressing the Vol Up + Home + Power Button.
3. In recovery mode, allow modifications. and under wipe there should be a button to format data. You will need to do this to flash Magisk and dm verity, if not your cellphone will be stuck on a bootloop.
4. Flash Magisk, when the process is done simply go back and flash dm verity. (this order is important)
5. Boot the phone normally, it shouldn't take long but don't worry if it takes up to 5 minutes. (In my case, when only the SAMSUNG logo showed up it would always keep going to a normal boot, but when it said A7 and the other info it would be stuck on a boot loop).
6. Open Magisk Manager app and check if you can download and install modules (it needs storage permission first). It you manage to install modules properly then skip to the next step. If it says Process Error and you can't seem to install modules then make sure you give the app the proper permissions and then on the home page of the app select Install Directly (Recommended), I guess this installs Magisk again or somethins.. This seemed to finally make it work for me. A reboot is necessary.
STEP 2
INSTALL SYSTEMLESS XPOSED FRAMEWORK SDK24 MODULE FROM MAGISK ALONG WITH MATERIAL DESIGN XPOSED INSTALLER APK
1. Get the latest "Material Design Xposed Installer" from here, it shouldn't matter if you immediately install it or install it later (like I did)https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758 (I'm 90% sure thats the one I used, if it doesn't work, try the one by Sr.CyanDroid)
2. In the Magisk Manager app, download and install the module XPOSED FRAMEWORK SDK24... It will tell you it installed correctly and reboot, you can double check by going into your Modules section after rebooting and seeing if it show up there... its a weird feeling but if it does show up that already means you successfully installed the xposed framework through Magisk.
3. Install (or just open if you previously installed it) the "Material Design Xposed Installer", it will either tell you it failed to detect Xposed or it will say its all perfect and you will be able to use Xposed normally. In case it says it failed, like it did to me, simply update the xposed app within itself. In my case, there was a notice at the bottom suggesting me to install the newest "Material Design Xposed Installer" and the problem was fixed immediately as I did it.
DONE
Keep in mind that by using this Magisk Method you are avoiding modifying the system partition, meaning its a lot less likely for you to brick your phone while trying different xposed files (apks are the only xposed files you need anyway). I hope this helps you and anyone else with this problem, keep in mind its 4am, and I'm really sleep so somethings MIGHT not be perfect. I also have a busy week coming up so I might not be able to respond any messages any time soon. Cheers!
Was looking exactly for this. Gonna try this in a day. Gonna post on the progress once done. Thanks!
If i did this, am i going to lose my warranty?
Sent from my [device_name] using XDA-Developers Legacy app
mido_many2000 said:
If i did this, am i going to lose my warranty?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes.
Will i lose my data ?