Xposed for Android 8- help needed - Magisk

Hello guys I recently rooted my xz premium dual sim and I currently have Magisk 22.1, I'm not an expert so
I need help please, what are a proper direct way to get xposed working properly on Android 8.0 ROM?
I mainly need to install XPrivacy, I tried to install EDXposed but it failed though and I'm not sure what to do
Thanks in advance

Since you need to install this with Magisk, do this:
Donwload the attached files
be sure to install the Xposed Magisk apk file first and open it it will show, thats it's not installed
then go to magisk and flash the xposed framework zip
and reboot
then (after your device is completely started with magisk and xposed) go to magisk, and check if the module's enabled. If it's NOT enabled, flash the zip again. If it's enabled, open xposed installer and check. (it's still not fully installed) and then there comes a message, that it's installed, but not really.
For the last step you need a custom recovery (like twrp or something)
Boot into your custom recovery and flash the xposed zip there (again)
Reboot and enjoy.
Another (way simpler) method would be to download it from magisk manager (if you have a older version) online repo.
I attached the Magisk version (with working repo)

In case xposed is installed but remains not active (yellow triangle instead of a green checkmark in the xposed installer app) follow the instructions of post #2 and don't worry you don't have to be an expert for this fix its fairly easy
Magisk + Xposed Framework is installed, but not active (XposedBridge.jar lacking)
Hi, new member here, who happened to lurk into XDA a few times in the past, and finally decided to register, hoping finding someone that would be able to help with my problem. I have Nexus 7 (2012), which became unusable with Android Lollipop...
forum.xda-developers.com

Related

No module after download and install?

Hallo forum
I just installed Magisk v.12 with the newest manger (MagiskManager-v4.3.3)
I have a wierd problem / bug?
Im trying to install "Sony framework" module
I can download and install , then magisk manager wants me to reboot and i do that, BUT after the reboot, theres no module installed under Module tab.
and when i search for the "Sony framework" its says not intalled - have also tested it with other modules -same problem
PLease help / advise
My device:
Teclast air x98 / Mirek190 rom
Thanks
This happens sometimes where the merging of the Magisk image doesn't quite work when installing from the Manager. Try installing from recovery instead.
Didgeridoohan said:
This happens sometimes where the merging of the Magisk image doesn't quite work when installing from the Manager. Try installing from recovery instead.
Click to expand...
Click to collapse
I have now flashed Magisk v12 with TWRP and have MagiskSU also
BUT
i still have the same problem ?
kekec777 said:
I have now flashed Magisk v12 with TWRP and have MagiskSU also
BUT
i still have the same problem ?
Click to expand...
Click to collapse
Install the module in TWRP...
Same problem. Using a Samsung Galaxy Tab 3 10.1 (GT-5220, it is a x86) using Lineage 14 7.1.2 with integrated Houdini.
Magisk and Hide is working well, Safety Net passes also.
When installing Sony Framework it is downloaded and installed and shows up in modules, but after the reboot it is not in modules anymore and in download section it has the not installed status. Flashing the ZIP using TWRP it causes a boot loop.
Did you find a solution meanwhile?
in my case, deactivating other Xposed module that i was using in the same time, resolved this issue ( it was module for spoof some phone/sim info) so try deactivate any other modules, and check again.

Magisk Manager "app not installed"

hello guys, hope you can help me here.
so as per title say, i got error when installing magisk manager 5.6.4, app not installed.
have try with older version but got same problem.
before this, i tried to upgrade system from nougat to oreo. successful with flashable roms.
at nougat, i got magisk manager, but couple steps to upgrade they recommended to remove magisk, so i use magisk uninstaller. and magisk gone for good.
after booting to oreo, i want to recover root, but cant even install magisk manager apk.
try to flash magisk 16.0, success with no problem.
now im very confuse. need help.
EDIT 1: and for some reason i cant install OTA. is this related?
Unfortunately I ran into the same problem. I tried installing Magisk Manager (5.6.3 and 5.6.4) on a stock, clean Nexus 6P but received that same error when running the app. I originally used ADB to install it and when that didn't produce the expected result I just used ADB to push the file to the device and then installed it manually. Neither method resulted in Magisk Manager running so I ended up having to install TWRP (which is what I was trying to avoid) and then flash the Magisk zip file. After that Magisk Manager ran successfully.
Too bad the documentation makes assumptions about everyone automatically understanding what is meant by 'install Magisk Manager'.
Sent from my Pixel 2 XL using Tapatalk

Magisk bricks my phone

I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.
I've been having zero luck getting this to work. Does anyone have any ideas?
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.
Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.
I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.

Bootloop - New fi Moto x4

I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!
Laugh this is just getting worse. I uninstalled Magisk and now the phone boots straight into recovery whenever I restart it. I'd flash a stock rom but I can't find one. I think I'm in trouble...
Reinstalled Magisk and it at least tries to boot up again but it just loops.
Arsenal420 said:
I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!
Click to expand...
Click to collapse
https://magiskroot.net/uninstall-magisk-module-twrp/
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
In summary:
Step 1: Download the flasheable zip file from the Magisk module uninstaller from the following link to the PC
Step 2: Send the zip file to the SD card of the phones or to the internal memory using MTP (most of the recovery of TWRP is compatible with this method)
Step 3: Now, touch the Install button and choose the Zip file of the uninstaller of the Magisk module that you want to update.
Step 4: After the completion of the installation. Go back to the TWRP home page.
Step 5: Tap the advanced option from the TWRP homepage. Choose the terminal option now.
Step 6: Type uninmod in the terminal box and touch the input button.
Step 7: Now, you can see the list of Modules and you have to type the Number you want to uninstall (Check the screenshot below)
Step 8: Finally, the magisk module will be completely uninstalled.
Arsenal420 said:
. Downloaded the Xposed Installed from the playstore,
Click to expand...
Click to collapse
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.
Nergal di Cuthah said:
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.
Click to expand...
Click to collapse
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?
Arsenal420 said:
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?
Click to expand...
Click to collapse
Ok good, I got scared for you a bit there, my post was not meant to be mean spirited but maybe you read it as such. As far as the bootloop i'm afraid i'll be no help.

Edxposed for S20 FE?

I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
I haven't need to use edxposed as I was refusing to upgrade from my old oneplus 3, so I'm a complete noob here at this point,
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Thanks!
everlasting207 said:
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Click to expand...
Click to collapse
Morning
I have just purchased the same phone, but I didn't get as far as you, so in the hope we can help each other here is a summary of what I did and how far I got -
I upgraded stock ROM all the way upto Android 11
Then enabled dev. options, and clicked on OEM unlock and then rebooted following the new unlock bootloader option on the download screen.
Then rebooted into download mode and flashed vbmeta_disabled.tar via ODIN (this then factor reset the phone).
Then had to re-flash stock android (via ODIN), as OEM unlock disappeared from dev. options.
Then back into download model to flash twrp 3.5.1 via ODIN.
Then after to trial and error and help from @afaneh92 I figured how to get into twrp recovery (and how to stop the phone from restoring stock recovery).
I then extracted & patched boot.img in Magisk (see instructions)
Then I booted back into download mode and 'tried to flash to new magisk patched boot.img via ODIN, but it failed with Can't open the specified file (line: 2006)
I then installed magisk manager 8.05, then tried flashing Magisk 21.2 via twrp and it failed with (Android Rescue party trigger).
So I then re-flashed multi-disabler.zip via TWRP and without rebooting formated data, then power off and boot back into recovery. I then flashed magisk 21.2 no problem.
Back into Android I loaded up magisk to confirm I was rooted and to get Riru & EdXxposed installed.
I installed EdXposed manager via its APK.
I then went back into Magisk manager and found and installed Riru 23.3 (this as i understand it replaced Riru - core).
I then found the latest stable version of EdXposed YAHFA 0.4.6.4 (4563) and this refused to install via magisk manager, with error ( ' Riru - core ' is not installed, Unsupported v22+ is installed, user 21.3 instead ) . So Clearly the above ver. of EdXposed isnt compatible with the latest version of Riru.
I then installed the alpha version of EdXposed 0.5.1.4 (4655) and this installed, but when I went into EdXposed manager it said it was installed but not active
So I have my shiny new SM-G781B, w/custom recovery & rooted, but no Xposed framework. I need Xposed for Xprivacy_lua so not having this running isnt an option. So I am going to try Riru - core 21.3/EdXposed_ 0.4.6.4 and if that fails then going all the way back to Android 10 and starting from the top.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What versions of Android, Twrp, Magisk, EdXposed, Riru - have you got installed? Also regarding your EdXposed bootloop - if you read the supports docs, its does say that YAHFA can cause soft loop, and to try Sandhook. But on my old S7, Sandhook caused a boot-loops so I went to and am using YAHFA with no issues - so as always your mileage will always vary.

Categories

Resources