Hey guys
I rooted my OPX at Kingroot.com on a Oxygen 2.1.2.
Im trying to install the Xposed framework (downloaded from the official forum: V75) but in recovery mode when I press the .zip file it just says "Installation failed"
Anybody know what i should do? - As said I have root access
The Xposed Installer just says that the framework is not installed and that i should download the latest ZIP file from XDA and then flash it manually via recovery. It gives me no option to install...
Others have installed the framework succesfully on the Oneplus forum..
Hope you can help
What recovery are you using? If you're using the stock recovery, then there's your problem. You'll need a custom recovery like TWRP.
If you are using TWRP, then the download might be corrupted. Try downloading it again.
What exact recovery (name and version) are you using? What exact file (full filename) are you trying to flash?
Hi folks,
i hope i im the right Forum as it seams more a xposed as supersu problem.
I have a Moto X Style rooted with System-less SuperSU 2.78 and Xposed "xposed-v86.1-sdk23" by romracer, Stock ROM 6.0.
Just got a notification that there is a security update available, proceeded but won´t flash. Stops with Error Code 7.
I thought OTA would work with system-less.
Tried also with disable Xposed. Same result. By the way when the phone reboots for flashing it goes into The Recover TWRP 3.0.2 GUI. Anyway i saw the error when switching to the log view.
Any idea whats wrong or i miss?
May i have to restore custom recovery, and if so can i flash the stock recovery with the existing TWRP or do i have to go ADB?
Thanks
Thomas
You have to flash stock recovery image (and probably also boot image) for OTA to work.
Simply use fastboot to flash those. Leave system intact.
Thanks, will do so.
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Jô$èph D said:
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Click to expand...
Click to collapse
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
Ok then ill give it a shot
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
I need to get stock boot img I don't have it pls help
Jô$èph D said:
I need to get stock boot img I don't have it pls help
Click to expand...
Click to collapse
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Can you pls link me the post for that file
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks
Jô$èph D said:
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks and I will stay active on this and other threads
Click to expand...
Click to collapse
Sure thing. See you around!
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
I wanted to use systemless xposed framework because the official version is not supported on my device. Also I wanted to use the modules that are specifically for magisk
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
Systemless xposed does not work either found this out earlier today device would not boot after installation of xposed through magisk
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
yaconsult said:
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
Click to expand...
Click to collapse
I will have to see if it works when a new version of magisk is launched.
I am really trying to do it by myself; I already tripped my knox 5x.
I am using sm-t713 and flashed sdk24 arm64 in TWRP, however ones I do it I stock in TWRP and unable to boot to system. Flashing xposed doesnt give me any errors. What am I am doing wrong. I am on [ROM] [7.0] Nougat - Stock Lite v3. I installed xposed installer pre and post flashing xposed in TWRP - no success.
Please help
netgar said:
I am really trying to do it by myself; I already tripped my knox 5x.
I am using sm-t713 and flashed sdk24 arm64 in TWRP, however ones I do it I stock in TWRP and unable to boot to system. Flashing xposed doesnt give me any errors. What am I am doing wrong. I am on [ROM] [7.0] Nougat - Stock Lite v3. I installed xposed installer pre and post flashing xposed in TWRP - no success.
Please help
Click to expand...
Click to collapse
Probably not waiting long enough after reboot.
ashyx said:
Probably not waiting long enough after reboot.
Click to expand...
Click to collapse
After flashing xposed in twrp. I am unablebto boot at all.
netgar said:
After flashing xposed in twrp. I am unablebto boot at all.
Click to expand...
Click to collapse
The best way to install Xposed is via Magisk.
Unroot your device completely by flashing the stock firmware or just the boot image then flash Magisk.
Open Magisk manager and install the Xposed module.
Nothing else required. All without affecting system or permanently breaking anything. It's as simple as removing the module to revert.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post67074423
ashyx said:
The best way to install Xposed is via Magisk.
Unroot your device completely by flashing the stock firmware or just the boot image then flash Magisk.
Open Magisk manager and install the Xposed module.
Nothing else required. All without affecting system or permanently breaking anything. It's as simple as removing the module to revert.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post67074423
Click to expand...
Click to collapse
Thx ashyx
I installed magiks and looks ok; still need to do more reading which kind of xposed to install
netgar said:
Thx ashyx
I installed magiks and looks ok; still need to do more reading which kind of xposed to install
Click to expand...
Click to collapse
You don't need to decide. The latest version is dynamic and will install the correct version.
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
der_andi01 said:
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
Click to expand...
Click to collapse
Your (custom) Recovery was really deleted?
Or replaced by stock Recovery
Who says that installation of Magisk requires custom Recovery?
Magisk documentation (Installation Instructions) - please find it on Magisk Github - certainly not.
Patch the boot.img and flash (it can be flashed by Fastboot, hence custom Recovery is not a must to have)
Hi,
it really gets deleted. My cell phone is then only in fastboot mode.
I am not interested in flashing Magisk either, but rather that recovery after an installation is no longer available. This makes installing updates more cumbersome.
I only have the problem when I flash a custom ROM. when I flash a MIUI ROM from xiaomi.eu Beta, the recovery is retained.