Database Users

Xposed Framework installation bricked Mediapad M3

hello everybody,
I bought the Huawei Mediapad M3, I unlock it’s boot loader and installing a new custom Recovery (Greatslon mod) and then flash SU, so the tablet has been correctly routed and everything worked perfectly.
Hounever I think: if you routed your device without install Xposed Framework , you don’t have many many important functions.
Later, I wanted to also install Xposed Framework, I followed the instructions for Marshmallow 6.0 provided by rovo89
but unfortunately when I reboot my M3 it going boot loops, I restored the system with the prior backup
and tried again with apk Xposed , but still the same boot loops, maybe there is something wrong in that Xposed.
Is there anyone who has found a solution to install Xposed Framerwork on Mediapad M3.

when i used marshmallow i used magisk v12 to root and then used systemless xposed v87 from there. worked for me. v87.1 disabled my fingerprint reader

trd_jzx100 said:
when i used marshmallow i used magisk v12 to root and then used systemless xposed v87 from there. worked for me. v87.1 disabled my fingerprint reader
Click to expand...
Click to collapse
I think it is not important how one rooted marshmallow if after everything works fine, but also i used
xposed v87 from there, and the result is boot loops, maybe it work well on other devices while on huawei mediapad m3 is not good

what I am trying to say is use the systemless xposed and it will work.

trd_jzx100 said:
what I am trying to say is use the systemless xposed and it will work.
Click to expand...
Click to collapse
thanks for your help, i will first try installing the Magisk interface, in order to install systemless Xposed with Magisk, and then i'll write the result

i flash Magisk , reboot the device, then i installed MagicManager.apk so i use MagicManager.apk to download and install automatically the right version of systemless Xposed framework, but when the device does the boot loader goes into the boot loop, i do not know what to do yet to run the xposed framework on my mediapad m3, i went crazy i never had trouble with various smartphones, i never had a tablet, damn the day i bought it, now i reset it to factory, and then i would like to make a final test before breaking it, do you can kindly list the various steps in the details you've been following, thank you in advance

well I am not sure then why your getting boot loops. so you have installedmagiskv12-then,magisk,manager and then go to module and flash the downloaded v87 framework there
link for v87 systemless frameworkhere
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268.
then after that install this it should be working but dont update to v87.1 or your fingerprint sensor might play up
link for the xposed apk
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758

thanks trd_jzx100,
at this time i brought my tablet back to the factory, before starting a new rooting procedure + installing xposed i would still have two questions:
1) after you made the unlock, which TWRP you installed to flash magisk?
2) i see from the link you posted that the xposed file you used is xposed-v87.0-sdk23-topjohnwu.zip instead i used xposed-v87-sdk23-arm64.zip maybe that was also a problem
later if all goes well, i will write the synthesis of the entire step-by-step procedure for the benefit of all mediapad m3 owners who want to do the same thing with no problems

finally xposed works, i used the system less rooting and then installed xposed v87 by topjohnwu,
now i have a issue with the xprivacy module but this is another story

trd_jzx100 said:
when i used marshmallow i used magisk v12 to root and then used systemless xposed v87 from there. worked for me. v87.1 disabled my fingerprint reader
Click to expand...
Click to collapse
Did you re-install when you got Nougat??? If so, can you help me out?

Which Magisk modules do you use?

So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..

These are my favorites so far, I am so happy with them

gonsa said:
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
Click to expand...
Click to collapse
It won't wipe your phone if you simply run it in fastboot and flash the TWRP recovery. The only reason it wipes the first time is because you had to do an oem unlock, which is already done now. The only time you will have to wipe your whole phone from now on is if you decrypt, and with ROMs starting to work with encryption, that shouldn't need to be done.
For the boot loop, my guess is a bad module.
To get the phone working again, you did the correct thing in flashing the stock zip without Magisk. The only thing you needed to do right after that was flash TWRP recovery image again through TWRP to overwrite the stock recovery. Then you would boot up, uninstall the modules, and reflash Magisk.
The only Magisk module I use is the stock Google Dialer/Contacts mod.

chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
Wow. Didn't knew there are so many modules just for OP5. Guess it's time to root.
Does using doze for Google play services causes any notification issues? Delay etc.

naturist said:
Wow. Didn't knew there are so many modules just for OP5. Guess it's time to root.
Does using doze for Google play services causes any notification issues? Delay etc.
Click to expand...
Click to collapse
None any issue, just flash and relax

ArkAngel06 said:
It won't wipe your phone if you simply run it in fastboot and flash the TWRP recovery. The only reason it wipes the first time is because you had to do an oem unlock, which is already done now. The only time you will have to wipe your whole phone from now on is if you decrypt, and with ROMs starting to work with encryption, that shouldn't need to be done.
For the boot loop, my guess is a bad module.
To get the phone working again, you did the correct thing in flashing the stock zip without Magisk. The only thing you needed to do right after that was flash TWRP recovery image again through TWRP to overwrite the stock recovery. Then you would boot up, uninstall the modules, and reflash Magisk.
The only Magisk module I use is the stock Google Dialer/Contacts mod.
Click to expand...
Click to collapse
thank you for your explanation. I managed to install the TWRP recovery again. what's happening now is I flash the ROM and it boots. I flash Magisk and it doesn't boot. I flash the ROM again and then SuperSU and it works. What I think is happening now is when I flash Magisk it might load the modules that don't work and it won't boot. Is there a way to know if the modules are installed in the background?
What I did now was flash the Magisk uninstaller and flashed the SuperSU and it's working.

Check out this guide I wrote!
https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727

Im_Mattgame said:
Check out this guide I wrote!
https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
Click to expand...
Click to collapse
I llaughed out loud when I read the "Flash Stock Recovery - Step 7/ Ponder for a minute at how useless it is"
You guide is good but not for my situation. I can boot, just not with Magisk. The thing was, I installed a lot of Magisk modules all at once, like Viper4Android, Emoji one module, and a bunch of more. Then rebooted and it bootlooped.

Would like to get center clock on the status bar. Is there a module that does this?

the_rooter said:
Would like to get center clock on the status bar. Is there a module that does this?
Click to expand...
Click to collapse
Substratum is your answer to that question. I haven't tried any full themes since our recovery is still a working mess it seems, so I'm worried about backups. But the Ozone Substratum module works well. I just made my clock centered with small date and am/pm. Persists through dirty flashes too.

the_rooter said:
Would like to get center clock on the status bar. Is there a module that does this?
Click to expand...
Click to collapse
This will do it
https://forum.xda-developers.com/oneplus-5/themes/v3-1-ozone-substratum-module-oos-t3627336

gonsa said:
thank you for your explanation. I managed to install the TWRP recovery again. what's happening now is I flash the ROM and it boots. I flash Magisk and it doesn't boot. I flash the ROM again and then SuperSU and it works. What I think is happening now is when I flash Magisk it might load the modules that don't work and it won't boot. Is there a way to know if the modules are installed in the background?
What I did now was flash the Magisk uninstaller and flashed the SuperSU and it's working.
Click to expand...
Click to collapse
I haven't had to mess around with uninstalling Magisk modules, but I assume the method to uninstall a module would be to
Flash system zip
Flash TWRP recovery
Boot into phone
Run the Magisk manager app without actually having Magisk installed
Uninstall or disable the modules
Then install Magisk

gonsa said:
I llaughed out loud when I read the "Flash Stock Recovery - Step 7/ Ponder for a minute at how useless it is"
You guide is good but not for my situation. I can boot, just not with Magisk. The thing was, I installed a lot of Magisk modules all at once, like Viper4Android, Emoji one module, and a bunch of more. Then rebooted and it bootlooped.
Click to expand...
Click to collapse
Ah okay I see, then yeah it is maybe an incompatibility issue with one of the modules, mind listing all of them, I'll try and figure out which one is causing the Bootloop ?

chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
Where I can find those zips?

FloyderE said:
Where I can find those zips?
Click to expand...
Click to collapse
just google it man

gonsa said:
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
Click to expand...
Click to collapse
Keep in mind that everytime you update your phone it will also install stock recovery. So you'll need to re-install twrp after every oos update.
I have no module installed but I use other apps that needs root.
Btw can anyone comment on atmos or viper4android, does your phone/headphone sound any better?

chazarss said:
None any issue, just flash and relax
Click to expand...
Click to collapse
How big of a difference on battery have you noticed using this doze Google play services module?

sl___ said:
How big of a difference on battery have you noticed using this doze Google play services module?
Click to expand...
Click to collapse
Not realy I can't say that really can fell

chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
So for the YouTube no ads, which one did you use, generic or Vance or black Vance?
Aldo for the arise module, do you have a link? I can't find it searching. Thanks.

i am using black version, so far soo good
Arise comes with magisk module in latest version from here https://www.androidfilehost.com/?w=files&flid=176171 but it is little complicated to install. but you can follow here for instuctions http://www.droidviews.com/install-arise-magnum-opus-sound-mod-android/

Pre-rooted ROM for XT1644?

Just updated xt1644 to June 2017 update+TWRP+ElementalX kernel. Having problem booting to system after Magisk v14 flash. Rolled back system and uninstalled all Magisk.
With no NFC and no future OTAs coming, I'm ready to try a pre-rooted ROM. Prefer one that is compatible with ElementalX but I can roll back to stock kernel. Also prefer support for E911 USA dialing. Any help appreciated.

Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The custom ROMs I've tested (Lineage, Invicta, RR) are compatible with ElementalX and others should be, a quick search of their support thread for ElementalX will reveal if others have tried it before.

echo92 said:
Before looking into custom ROMs, have you tried rooting with magisk 13.3? It's still available here at the bottom of the opening post https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.

mel2000 said:
OK, before completely giving up I'm going to try Magisk v13.3, which worked before. Thanks.
EDIT: Flashing Magisk v13.3 worked without a hitch. I installed Magisk Manager 5.1.1 as before. My only issue is that Magisk Manager keeps prompting me to install v14.0 after any option I select, even after rejecting the install option. There's also a status notification reminder. But I'm nervous about installing v14.0. Would it be advisable to to a Nandroid backup and then let Magisk Manager install v14.0? In any case, thanks for saving the day again echo92.
EDIT2: Tried installing Magisk v14.0 via Magisk Manage 5.1.1. Everything went well but again, the phone froze during the system reboot, just as before. Rolled back to Magisk 13.3 Nandroid backup and my system is working fine again without the latest Magisk update.
Click to expand...
Click to collapse
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)

HueyT said:
JX Nougat 8/17 modified stock ROM is fast, prerooted, and has 6/17 security update (used to be called CreamPie ROM)
Click to expand...
Click to collapse
Thanks HueyT, that looks like a good backup prospect. In the meantime I'll be doing some research on that ROM to see how well it fits.

Magisk hell resolved??!!!!!!!??!!!!!!!!!!??

im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR

works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!

I cant get to bypass safetynet V: other than that root works fine

J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed

Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.

desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...

try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431

also cant have xposed installed with the sn fix

G4 plus is bricking after installing Magisk?

Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?

What firmware or ROM are you currently running, and what version of magisk are you using?

kwebber321 said:
Recently i had a hard brick i had to do a recovery from. So far ive got everything back to working order with latest TWRP installed and everything is working with no problems since. But now I try to install Magisk through TWRP, have the latest version and Magisk manager installed, after its finished it dosent boot. I have to restore from my latest backup after. Also same thing happened when trying to install SuperSu. Anyway to fix this?
Click to expand...
Click to collapse
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.

ALPH000 said:
Before you root your device, you must replace your stock kernel.
Most people use ElementalX.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836/page192
Flash ElementalX through twrp, go through setup and then flash magisk. You'll do good.
If you're confused about ElementalX setup, go through installation tutorials.
Cheers.
Click to expand...
Click to collapse
Is there a custom kernel known to be compatible with the stock Pie ROM?

harryspar said:
Is there a custom kernel known to be compatible with the stock Pie ROM?
Click to expand...
Click to collapse
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793

echo92 said:
Do you mean the stock Oreo firmware? We don't have stock Pie
If so, there's ElementalX 3.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 or Loony: https://forum.xda-developers.com/moto-g4-plus/development/3-10-108-loony-kernel-t3726793
Click to expand...
Click to collapse
For Nougat, stock kernel is not rootable.
You have to replace it with elementalx kernel and then flash magisk.
However, when talking about Oreo stock firmware,
Situation gets inverted.
When flashed magisk with ElementalX 3.0.1, phone will not boot up.
And, stock kernel can be easily rooted by simply flashing magisk.
So, there is no need of ElemenralX kernel for rooting Oreo stock ROM unless you need it.

You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.

harryspar said:
You're correct. I meant Oreo.
On my device it never works. Not on the stock kernel, or elemental, or loony.
It boot loops until I run the Magisk uninstaller.
Click to expand...
Click to collapse
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?

echo92 said:
Hmm, that's odd - are you using magisk 19.3 or a recent version of magisk? When you flashed magisk, did you wipe cache before rebooting?
Is this behaviour observed on completely stock firmware (i.e. you've restored back to full stock Oreo, including a clean stock boot kernel)?
Click to expand...
Click to collapse
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.

harryspar said:
I think so. I will double check.
I actually don't need Magisk - my goal is to install Xposed. So in theory I could just try a different superuser. I'm just used to Magisk.
Click to expand...
Click to collapse
I hope you get xposed working on Oreo - if you do get magisk functioning, maybe this xposed plugin could work? https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Else there's edxposed https://forum.xda-developers.com/xposed/list-xposed-modules-android-pie-ed-t3892768 though I have no idea if xposed functions on stock Oreo.