Hello. Anyone know if there is a working version of xposed for the latest MIUI yet?
I tried installing the latest version from the magisk repository and was rewarded with a bootloop Thankfully uninstalling magisk modules from twrp is possible, but there's an hour of my life i'm not getting back.
Searching a bit and only turned up an issue in rovo89s github project - https://github.com/rovo89/Xposed/issues/408 - so I assume the answer is "no".
search EdXposed here in XDA, its working perfectly....
I'm on a custom MIUI 10 ROM based on the xiaomi.eu ROM. I'm in 10.2.1.0 and Xposed works for me.
My combination: Magisk 18.1 + Xposed Installer 3.1.5 Magisk version + xposed-v90-sdk26-arm64-beta1.zip
I cannot guarantee if this will work for you, or if every module works. I use only xInsta and my phone is perfectly stable..
you can try the V90_beta2 version,my MIUI 10 work fine,but you need disable resource hook.
Screenshot:
https://i.loli.net/2019/04/19/5cb967cde55a2.png
https://i.loli.net/2019/04/19/5cb967bdaf836.png
(My model is Mi5sPlus, I modified the model.)
Related
Official Xposed for Nougat is out,
Anyone tried it out on Sony's Stock ROM (e.g. 32.4.A.0.160) ?
Seems like the most important Modules are/were already working [feedback from the Unofficial Nougat variant]: https://forum.xda-developers.com/xposed/unofficial-list-modules-nougat-xposed-t3639615
Let's see if it also works with the official one,
that keeps the ART, JIT, etc. optimizations - so things might be different
Yes, it works. Gravitybox & Greenify installed.
Duvel999 said:
Yes, it works. Gravitybox & Greenify installed.
Click to expand...
Click to collapse
which version are you using? I've tried a few times always with bootloops.
I tried it with stock odexed rooted 1.54 7.1.1 ROM and it worked fine with some of my modules , other modules did not recognize the zposed FX presence in the system.
Tried it on e6633 w/ fw 2.33 : Stuck at boot after the logos have disappeared.
Edit: it works perfectly, just take a hell lot of time to boot (~10mins)
crisout said:
which version are you using? I've tried a few times always with bootloops.
Click to expand...
Click to collapse
Xposedinstaller 3.1.2 apk
Xposed v88 sdk25 arm64.zip
( Download uninstaller also => latest version 2016)
Gravitybox_Nougat 7.0.0 Alpha 01
Booting took some time.
Now on latest A.1.54 firmware without Xposed.
Flashed it on 7.1.1 .154 (the newest)
All my modules are working fine (tho first boot took very long, some may mistake it for bootloops)
Duvel999 said:
Xposedinstaller 3.1.2 apk
Xposed v88 sdk25 arm64.zip
( Download uninstaller also => latest version 2016)
Gravitybox_Nougat 7.0.0 Alpha 01
Booting took some time.
Now on latest A.1.54 firmware without Xposed.
Click to expand...
Click to collapse
Thanks, how much did it take? 10, 15, 20 minutes?
5-10 minutes. Take care for a charged phone.
greenify 3.7 is not compatible with the new xposed framwork. I am using this modules on stock 32.4.A.1.54 : 1-bootmanager 2-ambient display xposed 3-gravitybox 4-xinsta 5-xperiafmwohs
Took 7.5 minutes on my latest custom kernel here on 32.4.A.0.160 (7.1.1), now let's see what this puppy can do
s.hossein said:
greenify 3.7 is not compatible with the new xposed framwork. I am using this modules on stock 32.4.A.1.54 : 1-bootmanager 2-ambient display xposed 3-gravitybox 4-xinsta 5-xperiafmwohs
Click to expand...
Click to collapse
@s.hossein what features of GravityBox are you using ? do they work ?
Will it take that long every time you boot the phone? Or just the first time?
Because I installed xposed and thought it wouldn't get past the loading screen at all on my Z5, so I uninstalled xposed again.
But if it's only the first time booting I might reinstall it.
Noisecake said:
Will it take that long every time you boot the phone? Or just the first time?
Because I installed xposed and thought it wouldn't get past the loading screen at all on my Z5, so I uninstalled xposed again.
But if it's only the first time booting I might reinstall it.
Click to expand...
Click to collapse
No only first time takes longer. Use updated Xposed if available.
Yes. I know Xposed will work on PIE but it is not stable as you think.
It is UNOFFICIAL PORT, not UNOFFICIAL BUILD and will not work fully stable 100%.
https://www.xda-developers.com/xposed-framework-unofficial-port-android-pie/
I've tested it on HavocOS 2.1, on first boot it works but after I rebooted it, on second boot, something is going on. Other magisk modules that I have installed is gone, e.g. like in the Pixel Launcher, YouTube Vanced is gone but in the Magisk Manager, my modules are installed. And Magisk Manager won't detect root. Sometimes my device won't boot or will enter bootloop and requires to reboot again.
As stated on the thread.
Warning: Since the full source code of this unofficial port isn’t available, it may be risky installing this software on your device. There is a lot of discussion about this unofficial port on our forums here and here. While we can confirm it’s functional, we can’t confirm it’s safe.
Click to expand...
Click to collapse
So. Install at your own risk.
Has anyone been able to get this snapchat bypass version of edxposed working on their essential phone? I am currently on liquidremix rom (pie 9.0), I have tried both version 1.0.3 and 1.0.4, sandhook and yahfa, as well as the bootloop fix version, and all of them gets me stuck at boot animation.
https://github.com/Juxstin/EdXposed-SnapChat-Bypass/releases
Any help is appreciated. I really want to get snapchat working on my phone with edxposed.
Snapchat worked fine with edxposed (I think it was yahfa) on Pie for me, no "bypass" was needed. And this still holds true on Android 10 with Magisk + Edxposed.
Is the latest edxposed? You may need a custom magisk to start
The following is from the developer
---From Google Translation---
Notes: Since the above PR is not merged yet, to make those sepolicies present you have to use this build along with the customized Magisk build hosted here: https://github.com/solohsu/magisk_files.
Tanner1294 said:
Snapchat worked fine with edxposed (I think it was yahfa) on Pie for me, no "bypass" was needed. And this still holds true on Android 10 with Magisk + Edxposed.
Click to expand...
Click to collapse
not for me and quite a few other people in other threads. I get banned within a day or 2 with edxposed
I've been experimenting with different magisk mods on oxygen os 10 beta and found a complete working Dolby Atmos port that also doesn't crash gcam with dotfix like it used too on pie.
Here's the link for the Dolby Atmos magisk module
https://forum.xda-developers.com/showpost.php?p=81683221&postcount=4342
All I had to do to make it work was install a custom kernel and everything worked with no faults or crashes.
My choice of kernal was the latest blusparks kernel but should work with all the popular ones
Update:
I did some testing and can confirm the latest module through the thread posted works...
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508/page473
Use the Google drive link provided in comments on that page and download Dolby rc4 because rc5 is faulty and will be taken down.
Also download the acdb module in that Google drive link and install that too.
This now makes it work without clashing with OnePlus audio FX aswell as keeping the device certificate as OnePlus instead of Sony like it was with the last module posted. All still works with gcam and dotfix.
For reference my device is on oos10 stable and has blusparks custom kernel and selinux is set to permissive as some people mention it makes Dolby crash with enforcing.
I flashed this "blu_spark_r198-oos_op5-op5t_8ba46c0b8.zip" Kernel on OOS10 Beta 2 but not boot the device
You will have to flash stock kernel to recover from that if not reflash the ROM over your existing install should be fine... That isn't a problem with the Dolby module and to be fair doesn't happen to anyone on the blusparks forum page so something with that install definitely went wrong I would post a logcat of sorts on their page and see if the answer can be found there. Like mentioned you can use any supported custom kernel for your ROM if you can't get blusparks working which I am very sure is some error in the install process as that's not normal than you could use new kernel or lazy kernel to name a few.
I can't explain better without knowing your exact process you took but can guarantee that is not the normal outcome for installing this or any kernel for boot loop something you have done or the zips install process has made an error sorry
Like I said for support on the kernel check with the developer on his page sorry you had this problem
Are you flashing Magisk Canary or Magisk Stable? Magisk Canary builds after Magisk Stable 20.4 currently cause bootloop but will likely be fixed in a later Magisk release (no ETA).
That was on the first and last page of the blusparks kernel thread which I would recommend quickly reading through any mods thread before installing it to know if you can use it or if you will gain problems.
Not sure if this applies to you but that's the only mention of bootloops in the last year or so on that thread. Hopefully this might help you
You just have to set selinux to permissive.
The app is not turning on
dDranzer said:
The app is not turning on
Click to expand...
Click to collapse
it's the same with me
Other than making sure ityou are using selinux set as permissive and having a custom kernel there isn't anything that can go wrong but I ain't doubting it ain't working for you.
Try my setup which is using blusparks kernal other than installing that I have done nothing else so if not working there must be another module or something that's stopping this from happening. Even though what your explaining usually points to your selinux being enforcing as that's what every Dolby has done for years it either opens but won't power on or it crashes and closes as opening.
I can confirm I personally have 3 OnePlus 5t devices in my house that all have this working under the latest stable oxygen os 10 with the latest gcam and dotfix installed and only had to install bluspark to make dolby open up.
By the way for anyone using this module the only one I know supported is the zip in the link posted. Not the rest of the modules from that thread, atleast none I've tried so if you want it to work don't try searching for newer versions through that thread.
If you do find a more updated version or a fix for the ones posted newer than this module please inform us all through this thread.
Thank you so much ahh! I love this compare to a viper in my opinion.
Has anyone else noticed that magisk has stopped working? The latest addition? There is no longer any access to hide magisk features with the latest features?
For instance for Pokemon Go to work on a custom rom you need magisk hide to hide magisk an hide from app.
I cannot even get it to open after it forces update?
Bryceicle1971 said:
Has anyone else noticed that magisk has stopped working? The latest addition? There is no longer any access to hide magisk features with the latest features?
For instance for Pokemon Go to work on a custom rom you need magisk hide to hide magisk an hide from app.
I cannot even get it to open after it forces update?
Click to expand...
Click to collapse
Happy new year. Maybe reinstall Magisk manager? For me it works perfectly, just be sure to install 21.2 magisk and you should be good to go.
Slim K said:
Happy new year. Maybe reinstall Magisk manager? For me it works perfectly, just be sure to install 21.2 magisk and you should be good to go.
Click to expand...
Click to collapse
I actually listened to another members post an have had success flashing an rooting 3 roms that I could not do either of those with. Apparently there is some kind of conflict bwteeen something in android 10 an android 11. So Ofox 12.0.6 an global firmware for surya 12.0.3.0 are the solutions.
Magish 21.0 worked every time with an android 11. Neither 21.1 or 21.2 worked for me with A11 roms. Only magisk 21 had full functionality
Bryceicle1971 said:
I actually listened to another members post an have had success flashing an rooting 3 roms that I could not do either of those with. Apparently there is some kind of conflict bwteeen something in android 10 an android 11. So Ofox 12.0.6 an global firmware for surya 12.0.3.0 are the solutions.
Magish 21.0 worked every time with an android 11. Neither 21.1 or 21.2 worked for me with A11 roms. Only magisk 21 had full functionality
Click to expand...
Click to collapse
Weird . For me it was the opposite. I had to flash global MIUI 12.0.4.0 to make anything custom work. Until I upgraded to 12.0.7.0, ever since everything works perfectly. Magisk below 21.0 never worked for me on this device.
I have a hypothesis, that all device variants (Indonesian, European, global, Russian) have different vendors and not 100% compatible, Maybe different modem configuration as well. I noticed in mine (European version) that LTE battery consumption is a lot better (by 2hrs SOT!!!) so i'm confused on what to do. Should I stay on MIUI with all it's issues or switch to a custom ROM and lose 1-2 hours of screen on time.
Slim K said:
Weird . For me it was the opposite. I had to flash global MIUI 12.0.4.0 to make anything custom work. Until I upgraded to 12.0.7.0, ever since everything works perfectly. Magisk below 21.0 never worked for me on this device.
I have a hypothesis, that all device variants (Indonesian, European, global, Russian) have different vendors and not 100% compatible, Maybe different modem configuration as well. I noticed in mine (European version) that LTE battery consumption is a lot better (by 2hrs SOT!!!) so i'm confused on what to do. Should I stay on MIUI with all it's issues or switch to a custom ROM and lose 1-2 hours of screen on time.
Click to expand...
Click to collapse
I've sorted everything out. I recommend the firmware you already use for android 11 custom roms. One rom I read other guides for an watched YouTube guides. It's EvolutionX 5.2. It has basically converted my Poco X3 NFC global into a Google pixel 5.
This rom is head an shoulders the best rom for our device. It only needs firmware 12.0.7.0. Which I also found solved all issues an to be flashed from the phones internal memory.
It's beautiful. No bugs. I only use that new twrp ending in 15 an magisk 21. Newer magisks fail to root.
But yes could be to do with different countries.
Edit: Evolution is not the highest benchmarking. An is not the fastest. Its an all round rom for daily driver use. Antutu bench's in the mid 270-280k area.