Hi everybody!
I'm trying to install Xposed framework on an Android x86 - v89, 7.1.2, SDK25 (installed over VirtualBox).
So I followed the official thread, and downloaded the apk and the zips for SDK25, version 89.
Than I unzipped the zips into the sdcard folder, copied exposed.prop to /system
and run flash-script.sh from the terminal (of the android x86),
than rebooted.
But when I open the Xposed installer app it says:
"Xposed framework version 89 is installed, but not active. Please check the logs for details."
When I'm trying to view the logs I get the message:
"Cannot read log/data/user_de/0/de.robv.android.xposed.installer/log/error.log (No such file or directory)".
I tried to do everything I found in order to fix it,
Gave permissions to the Xposed installer,
Created the error.log file myself,
Reinstalling the all Xposed (zips, and apk),
Reinstalling the all Android x86 OS,
And everything I found online..
I really looked out to every tutorial I found online but nothing actually helped or fit the Android x86 (involved Recovery mode which is not available in Android x86).
Anyone ever did such thing or can help me?
Thanks for your help in advanced,
James T. :fingers-crossed:
After a bit of searching and experimentation I was able to get EdXposed (YAHFA variant) working on my Galaxy A70 with Lineage OS 17 (never had problems with Magisk itself, just EdXposed).
FILES
lineage-17.0-20191203-UNOFFICIAL-a70q.zip
TWRP 3.3.1-0
Magisk Manager_7.5.2-b39f4075 0dc9f5c3.apk (Canary) EDIT: Corrected file version.
Riru_-_Core-v19.6(28).zip
Magisk-v20.4-0dc9f5c3(20303).zip
magisk-EdXposed-YAHFA-v0.4.6.0_beta.4471.-release.zip
EdXposed Manager 4.5.4.apk
The LOS I used is an older version (not sure if this has anything to do with anything, but thought I'd mention it). I chose YAHFA instead of SandHook because I've had better results in the past on other devices.
The Magisk files are a combination of 'Standard/Stable' builds, and Canary builds. For Canary files, start here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
PROCEDURENot sure if reboots are required after each flash, but I did them. Assume LOS & TWRP 3.3.1-0 already installed.
Install Magisk Manager—>Riru Core within it
From TWRP flash Magisk
Within Magisk Manager flash magisk-EdXposed
Install EdXposed Manager
The 99% reason I needed EdXposed was for XprivacyLua, and it's working fine. Here's some other Xposed modules I'm using, although BootManager might not be actually doing anything (haven't tested yet), it's not causing any problems.
Xprivacy Lua
MinMinGuard
Scoop
BootManager
Statusbar download progress
Xposed Edge
[EDIT] EdXposed is showing this error when hitting 'Download':
Downloading https://dl-xda.xposed.info
/repo/full.xml.gz failed: Chain validation
failed
...but I can live that. Just install modules like any other .apk
[EDIT] For some reason, absolutely no idea why, 'Download' in EdXposed now working as expected.
that's great thanks for your contribution to help A70 users.
TiTiB said:
After a bit of searching and experimentation I was able to get EdXposed (YAHFA variant) working on my Galaxy A70 with Lineage OS 17 (never had problems with Magisk itself, just EdXposed).
FILES
lineage-17.0-20191203-UNOFFICIAL-a70q.zip
TWRP 3.3.1-0
Magisk Manager_7.5.2-b39f4075 0dc9f5c3.apk (Canary) EDIT: Corrected file version.
Riru_-_Core-v19.6(28).zip
Magisk-v20.4-0dc9f5c3(20303).zip
magisk-EdXposed-YAHFA-v0.4.6.0_beta.4471.-release.zip
EdXposed Manager 4.5.4.apk
The LOS I used is an older version (not sure if this has anything to do with anything, but thought I'd mention it). I chose YAHFA instead of SandHook because I've had better results in the past on other devices.
The Magisk files are a combination of 'Standard/Stable' builds, and Canary builds. For Canary files, start here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
PROCEDURE
Not sure if reboots are required after each flash, but I did them. Assume LOS & TWRP 3.3.1-0 already installed.
Install Magisk Manager—>Riru Core within it
From TWRP flash Magisk
Within Magisk Manager flash magisk-EdXposed
Install EdXposed Manager
The 99% reason I needed EdXposed was for XprivacyLua, and it's working fine. Here's some other Xposed modules I'm using, although BootManager might not be actually doing anything (haven't tested yet), it's not causing any problems.
Xprivacy Lua
MinMinGuard
Scoop
BootManager
Statusbar download progress
Xposed Edge
[EDIT] EdXposed is showing this error when hitting 'Download':
Downloading https://dl-xda.xposed.info
/repo/full.xml.gz failed: Chain validation
failed
...but I can live that. Just install modules like any other .apk
[EDIT] For some reason, absolutely no idea why, 'Download' in EdXposed now working as expected.
Click to expand...
Click to collapse
Hello there.
I managed to install edxposed on Samsung A70 with stock android 9.
It's working fine, module's works.
But what I have been experiencing is that the phone has gotten very sluggish. The more modules I install the more it hiccups.
I currently have firefds kit [p], adblock reborn, edxposed manager and flat style indicator icons only.
Any advise?
I no longer own the A70...so, no. The only reason I saw your post is because I still had this thread bookmarked. Hopefully someone else has some useful info. gl
Can confirm.
Disabling the xposed modules fixed the lag.
Guess this is how its going to be
I have a module development question. I don't know exactly where to post this question. If this is not correct place, would you please show me the correct place?
I rebuild an old xposed module and generate signed APK. I can install and use this APK on android 6 and 7 systems with standard Magisk and Xposed. And works perfectly.
But when I use this APK with android 9 and Magisk, riru and edxposed, phone can't be booted. it falls into edxposed bootloop.
When I it use it with Magisk, Zygisk and LSPosed, I can install APK, enable it on LSPosed, but does not function as expected.
When I try to install original old module from repository, it is not possible to install this APK to android 9.
This is the original old module:
LeEco Infrared Fix | Xposed Module Repository
repo.xposed.info
I had to upgrade gradle version and several other configurations to build successfully. It can be running up to android 7, not tried but probably will run up to Android 8. But it is not possible to run android 9 or later.
How can I debug the code, and understand why edxposed fall into bootloop. Are there any log file to examine?
Thanks
Hello everyone. I have a Samsung S20. I wish I could install edxsposed framework to install various modules. I rooted my device, installed riru v.26.1.4, but when I try to install edxposed vers. 0.5.2 gives me error saying riru is not installed.
I tried to install the version of riru vers. 25.0 and at that point edxposed installs it for me but crashes when starting the app.
I have android version 13. Can you help me please? thanks a lot to everyone
Hi guys,
new here and went through quite a few threads on Magisk before posting.
Situation is as follows:
- got my Xiaomi Mi 11 Ultra from Aliexpress a few days ago.
- the seller unlocked the bootloader and instealled global ROM instead of the original Chineese ROM.
- the phone works fine, but Google Wallet would not allow me to add any of my credit/debit cards for contactless payments showing the usual "Your phone doesn't meet security requirements"
- NETFLIX wouldn't work.
- Quite a few of my banking apps work fine, including HSBC bank, Paypal, Revolut, IG Index and some others as well.
The obvious solution is to go ahead with Magisk Hide (or what's currently available instead as Hide module is phased out as far as I understand).
Now, I'm really new to all this (have rooted a couple of phones/tablets a few years back) and have a few questions:
1. I was going through the process of installing Magisk on my phone, folloing the instructions here: https://www.xda-developers.com/how-to-install-magisk/?newsletter_popup=1
So according to this, I'm supposed to find a boot.img file in the ROM archive as far as I understand, but my issue is that I don't have the installed ROM details or data as it wasn't me who installed the ROM in the first place.
Is there any way to find out what ROM is installed and perhaps I could download the package and get the boot.img file from there? (ramdisk parameter show YES)
2. I will be installing ADB on my computer to be able to install Magisk as per the following instructions: https://www.xda-developers.com/install-adb-windows-macos-linux/
is there anything else I'd need?
3. Lastly, there is a bunch of good tutorials on your tube on how to use the latest Magysk + shamiko module etc. If someone knows a really good one, I would appreicate if you could post it
Would really appreciate any other feedback etc for a person who is completely new to this
Thank you very much!
I'm not sure how to completely proceed as I am totally unfamiliar with Xiaomi, but I had a couple of ideas...
Kotofeus said:
- the seller unlocked the bootloader and instealled global ROM instead of the original Chineese ROM.
The obvious solution is to go ahead with Magisk Hide (or what's currently available instead as Hide module is phased out as far as I understand).
Now, I'm really new to all this (have rooted a couple of phones/tablets a few years back) and have a few questions:
1. I was going through the process of installing Magisk on my phone, folloing the instructions here: https://www.xda-developers.com/how-to-install-magisk/?newsletter_popup=1
So according to this, I'm supposed to find a boot.img file in the ROM archive as far as I understand, but my issue is that I don't have the installed ROM details or data as it wasn't me who installed the ROM in the first place.
Click to expand...
Click to collapse
I imagine you can find exactly what ROM you are using in the Settings -> "About Phone" or something similar; Probably under something like "Android version" or "Build number". You can google search (most likely by build number or something similar) and find the Factory image needed to flash/install the ROM. Once you download that specific ROM installation file (most likely a .zip file), you should be able to extract it (or go inside the zipped file and extract the specific boot.img file) to be able to patch it in Magisk.
Kotofeus said:
2. I will be installing ADB on my computer to be able to install Magisk as per the following instructions: https://www.xda-developers.com/install-adb-windows-macos-linux/
is there anything else I'd need?
Click to expand...
Click to collapse
Best place to get the adb (and you'll also need fastboot.exe so you'll also get it from) is from the Platform Tools from Google's developer's site here: https://developer.android.com/studio/releases/platform-tools
I'm unsure (but I doubt) if Xiaomi Mi 11 Ultra has 2 slots (A and B), but if it does, don't download the latest version of platform tools but version r33.0.3 because any version r34.0.0 and above has a known bug that will wreck devices with 2 slots (namely Google Pixels).
Anything else you'd need is to be sure to have USB debugging enabled and the proper Google USB drivers installed on your computer (there are Windows, Mac, and Linux drivers that can be installed).
Kotofeus said:
3. Lastly, there is a bunch of good tutorials on your tube on how to use the latest Magysk + shamiko module etc. If someone knows a really good one, I would appreicate if you could post it
Click to expand...
Click to collapse
There are a number of root hide methods that hide root from Netflix and Google Wallet. One usually starts with using Magisk and Zygisk Denylist and making sure that Wallet, Netflix, Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework are all "ticked" with all their sub-selections ticked as well. Also, be aware that after implementing any/all of these, usually clearing all these Google services data and cache is required & a reboot of the device is a must, but re-entering your cards will also be required as well; as well as signing back into some Google services. Then, if all that doesn't work, there's Universal SafetyNet Fix -- or even Displax's Mod branch if the official USNF isn't enough. Then also any of the further root hiding methods; Shamiko, Magisk Delta, HideMyApp, etc..
Kotofeus said:
Would really appreciate any other feedback etc for a person who is completely new to this
Thank you very much!
Click to expand...
Click to collapse
Again, I'm coming only from Pixels and have absolutely no experience with Xiaomi and I can't be sure any of these will apply since you have a "custom" ROM (sort of) so things might not be as usual. These are just general dealings with Magisk and Android OS as I know them... But you state that you are "completely new to this", so I'm just trying to cover all the bases as much as I can, even if you would be already knowledgeable of them. If anything, these can be taken as just ideas and/or pointing to a direction that might work...
simplepinoi177 said:
I'm not sure how to completely proceed as I am totally unfamiliar with Xiaomi, but I had a couple of ideas...
I imagine you can find exactly what ROM you are using in the Settings -> "About Phone" or something similar; Probably under something like "Android version" or "Build number". You can google search (most likely by build number or something similar) and find the Factory image needed to flash/install the ROM. Once you download that specific ROM installation file (most likely a .zip file), you should be able to extract it (or go inside the zipped file and extract the specific boot.img file) to be able to patch it in Magisk.
Best place to get the adb (and you'll also need fastboot.exe so you'll also get it from) is from the Platform Tools from Google's developer's site here: https://developer.android.com/studio/releases/platform-tools
I'm unsure (but I doubt) if Xiaomi Mi 11 Ultra has 2 slots (A and B), but if it does, don't download the latest version of platform tools but version r33.0.3 because any version r34.0.0 and above has a known bug that will wreck devices with 2 slots (namely Google Pixels).
Anything else you'd need is to be sure to have USB debugging enabled and the proper Google USB drivers installed on your computer (there are Windows, Mac, and Linux drivers that can be installed).
There are a number of root hide methods that hide root from Netflix and Google Wallet. One usually starts with using Magisk and Zygisk Denylist and making sure that Wallet, Netflix, Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework are all "ticked" with all their sub-selections ticked as well. Also, be aware that after implementing any/all of these, usually clearing all these Google services data and cache is required & a reboot of the device is a must, but re-entering your cards will also be required as well; as well as signing back into some Google services. Then, if all that doesn't work, there's Universal SafetyNet Fix -- or even Displax's Mod branch if the official USNF isn't enough. Then also any of the further root hiding methods; Shamiko, Magisk Delta, HideMyApp, etc..
Again, I'm coming only from Pixels and have absolutely no experience with Xiaomi and I can't be sure any of these will apply since you have a "custom" ROM (sort of) so things might not be as usual. These are just general dealings with Magisk and Android OS as I know them... But you state that you are "completely new to this", so I'm just trying to cover all the bases as much as I can, even if you would be already knowledgeable of them. If anything, these can be taken as just ideas and/or pointing to a direction that might work...
Click to expand...
Click to collapse
Thank you very much for taking time and going through all my queries, really appreicate it!
I started losing hope really as looked through a number of vide tutorials involving installing magisk via custom recovery, which would mean I needed to install a custom recovery first... so this was becoming a bit of a Russian Doll thing and a never ending quest.
Looked at "Detailed info and specs" on my phone and I have:
Baseband version
Kernel Version
I presume I can search by Kernel Version to find the ROM - will try that.
If I can't find the ROM, than the only way is to try and install custom recovery, download Magisk apk, rename it into zip, get into custom recovery mode and try to flash the zip file. Saw a few tutorials on youtube like that and it looked fairly straightforward, however not sure how easy or difficult it would be to install a custom recovery like TWRP on this phone.
I also looked through a tutorial of using Magisk with Zygisk and Denylist and again, looked pretty straightforward, but Magisk needs to be properly installed of course.
Yes, thank you - I understand that you need to clear cash and re-enter the cards once again, that would have been the least of my troubles.
Will try to search that kernel number on google once I have a moment and see if I get any luck.
Will also reasearch on how to install TWRP. If that's easier than I may go with that option instead of extracting and patching the boot.img
Kotofeus said:
Looked at "Detailed info and specs" on my phone and I have:
Baseband version
Kernel Version
I presume I can search by Kernel Version to find the ROM - will try that.
Click to expand...
Click to collapse
You can't find what MIUI version you have? That's all you basically need...
From a small bit of research, you state you are on a "global ROM" of a Xiaomi Mi 11 Ultra, which should just be a "global" version of the MIUI. You just need to find the MIUI global version and extract it (boot.ini) from the firmware update file. Once you find the version, you could search and find the firmware update file in places like here: https://xiaomirom.com/en/rom/mi-11-pro-ultra-11-ultra-star-global-fastboot-recovery-rom/ or other sites I imagine.
It's just important that you get the exact right version of the MIUI Global ROM you are currently running as patching and flashing a boot.ini of a different version could soft-brick/bootloop your device....