I installed Xposed on BlueStacks (rooted) and install Xposed Framework: de.robv.android.xposed.installer_v29_665be7.apk.
Trying to install/update the framework and get this following errors:
Copying Xposed-Diabler-Recovery.zip...
Mounting /system writable...
Segmentation fault
Could not mount /system writable
Trying to continue anyway...
Segmentation fault
Failed to create a backup of /system/bin/app_process
I update my SuperSU and installed BusyBox. But nope, i get "please flash the xposed-disabler-recovery.zip in SD Card"
Why am i get this following issue?
Is Xposed can't be run/installed in x64 PC??
Seems like you did many things already, except for reading the OP. There's a link to an additional app that you need to install.
Or just check the FAQ / Known issues thread.
rovo89 said:
Seems like you did many things already, except for reading the OP. There's a link to an additional app that you need to install.
Or just check the FAQ / Known issues thread.
Click to expand...
Click to collapse
what link??
dhrumilshah49 said:
what link??
Click to expand...
Click to collapse
Check the FAQ, it's there.
Related
I'm trying to install xposed framework on my little brothers Kyocera Hydro. I was able to root it and give the installer root permissions but then I get this error. Can anyone tell me what this is about and it I can get around it. Its running android 4.0.4 which meets the requirements so I'm a bit lost at what could be the issue.
HTML:
SD card: /mnt/sdcard/Android/data/de.robv.android.xposed.installer/files
Coping Xposed-Disabler-Recovery.zip...
Mounting /systemwritable...
Segmenation fault
Couldn't mount /system writeable
Trying to continue anyway...
Segmentation Fault
Fail to create backup of /system/bin/app_process
Read the FAQ.
GermainZ said:
Read the FAQ.
Click to expand...
Click to collapse
Or assuming that the latest version if being used, read the red warning text that is displayed afterwards on the main window
xposed
Tungstwenty said:
Or assuming that the latest version if being used, read the red warning text that is displayed afterwards on the main window
Click to expand...
Click to collapse
so you want to use an older version_ sdk15 _it works fairly well
Hi @rovo89 , so here is the situation
I've:
-installed BS 0.8.8.8006 - OK
- ROOT (1) with BSMT - OK
- disable auto update (6) with BSMT - OK
- install superuser (S) with BSMT - OK
- xposed installer (X) with BSMT -OK
Then I click install/update in framework , I grant the super user permission to Xposed, then got an error
"SD Card :/mnt/sdcard/Android/data/de.robv.android.xposed.installer/files
Copy of Xposed-Disabler-Recovery.zip...
Mount of /system in writing...
Segmentation fault
Impossible to mount /system in writing
Continue anyway...
Backup already exists at /system/bin/app_process.orig
Copy of app_process...
Segmentation fault
impossible to copy app_process to / system/bin
(sorry for the translation the original message is in french)
It's written in red " It seems you have a known problem ( "Segmentation fault")with your ROM. Install the Framework Xposed might not work or make problems . Click here for more details."
When I click it suggests to install busybox. I've tried to install them and then reboot. But now it never starts !
So I've done all the steps again and now I got the error message again...
Please any suggestion will be appreciated.
Regards
I'd recommend using Genymotion instead of Bluestacks, as Xposed installs fine on it. I might be wrong but I don't see rovo trying to "fix" Xposed to work with a closed source emulator with heavy modifications from what I've seen.
I just installed Alliance rom on my att gs5. For some reason it won't let me install xposed framework. Help?
I have the same problem with gt-n8013 cyanogenmod rom
"It won't let me install Xposed framework" – how so? Any errors?
I can't submit a screenshot of the error because I don't have many posts. But it says "Failed to create a backup of /system/bin/app_process
There should be an error above/below that line as well? Have you tried installing Xposed via the recovery?
It's a big error. Its a lot to type but tldr it says permission denied. No, how do I do that?
Rennocc said:
It's a big error. Its a lot tof type but tldr it says permission denied. No, how do I do that?
Click to expand...
Click to collapse
Permission denied? Are you sure you're rooted (if you are, double check that the Xposed Installer is granted root permissions)?
You can install it via the recovery by changing the installation method (press the button).
I have no idea what I did but I tried to install it again and it worked so. Thanks for trying to help but its fixed now haha.
Help
Having trouble with loading Netflix so discovered about the xposed fix for this problem. I tried to install xposed but got the "signature" error message which I believe tells me xposed is already installed. In my "apps", I do not have xposed listed as an installed app. Doing a file search, there are no hits on "xposed". I recently upgraded to latest Beanstalk 4.4.4. Any help would be appreciated. Thank you.
I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc
Do you have a folder called init.d in system/etc?
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not
Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be
Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.
gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1
Universal init.d install it from play store and follow instructions
miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?
trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?
dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.