Database Info

(XPOSED)OFFICIAL XPOSED FOR MI A1 using flashfire

Official Xposed Working perfectly,
Root your MI A1 by following this instructions
https://forum.xda-developers.com/mi-...pdate-t3681024
Please carefully watch these steps to root..your phone...
Then we are gone for xposed..
Download the xposed installer.zip
http://dl-xda.xposed.info/framework/sdk25/arm64/
Flash the zip file using Flashfire app...then install,
XposedInstaller_3.1.2.apk
https://forum.xda-developers.com/showthread.php?t=3034811

Not working.

It's working perfectly...
Screenshot prof...

is this module works for you?
they say it works for Nougat too
https://forum.xda-developers.com/xposed/modules/mod-fingerprint-enabler-t3411066
when screen is locked by third party app (some launcher, 3rd party tile, etc) fingerprint on Mi A1 cannot unlock the phone.
that module enables that.

Tried as you wrote: flashed the xposed zip file using flashfire -> reboot -> xposed framework wasn't installed.
Then I tried to install xposed framework using the xposed app -> worked
=> Just install xposed installer apk and install xposed framework using the app.
Edit: I forgot that there was this thread: https://forum.xda-developers.com/mi-a1/how-to/install-xposed-flashfire-recovery-t3685713

https://forum.xda-developers.com/mi-...pdate-t3681024
link not working

its worked used xposed installer v3.1.2
gavitybox work fine too....

Yup gravity box works very well. Pleased with the way development is happening & being an AOSP we will get our fair share.

thanks for sharing~

AndroidAdvisor said:
Official Xposed Working perfectly,
Root your MI A1 by following this instructions
https://forum.xda-developers.com/mi-...pdate-t3681024
Please carefully watch these steps to root..your phone...
Then we are gone for xposed..
Download the xposed installer.zip
http://dl-xda.xposed.info/framework/sdk25/arm64/
Flash the zip file using Flashfire app...then install,
XposedInstaller_3.1.2.apk
https://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
It does not work, when i flashed it via flashfire, i got still black screen for over 30minutes, so i gave up and forced it to reboot...
Then i've got bootloop.....
When i tried to install it via xposed app i got this error:

ves626 said:
It does not work, when i flashed it via flashfire, i got still black screen for over 30minutes, so i gave up and forced it to reboot...
Then i've got bootloop.....
When i tried to install it via xposed app i got this error:
Click to expand...
Click to collapse
i think it's was magisk that caused error.
i used supersu for root.
Sent from my Mi A1 using Tapatalk

ves626 said:
It does not work, when i flashed it via flashfire, i got still black screen for over 30minutes, so i gave up and forced it to reboot...
Then i've got bootloop.....
When i tried to install it via xposed app i got this error:
Click to expand...
Click to collapse
this is because ur have rooted ur cell with magisk
root it in supersu

Hellrazoraj said:
Yup gravity box works very well.
Click to expand...
Click to collapse
That was everything I was looking for. Thanks for the advice

AndroidAdvisor said:
Official Xposed Working perfectly,
Root your MI A1 by following this instructions
https://forum.xda-developers.com/mi-...pdate-t3681024
Click to expand...
Click to collapse
Just wanted to point out that the link you've given there comes out as "https://forum.xda-developers.com/mi-...pdate-t3681024" and leads to a 404.

guys i have flashed magdisk and it works and now im trying to flash systemless xposed via recovery and i get this:
/system could not be mounted
Error installing zip file...

faddys123 said:
guys i have flashed magdisk and it works and now im trying to flash systemless xposed via recovery and i get this:
/system could not be mounted
Error installing zip file...
Click to expand...
Click to collapse
Hey buddy, I will root my phone & share the steps(screenshots) with you by tonight

Hellrazoraj said:
Hey buddy, I will root my phone & share the steps(screenshots) with you by tonight
Click to expand...
Click to collapse
i had to flash a file called sysmount and then i flashed the systemless xposed but it told me that i need magdisk v14 or higher :/

ArchitDewari said:
this is because ur have rooted ur cell with magisk
root it in supersu
Click to expand...
Click to collapse
This is the answer to all having magisk and trying to get Xposed

I just did the following procedure:
flashed official rom with miflash,
booted to rom,
intalled second october OTA update (75mb),
booted twrp with "fastboot boot recovery.img",
and then:
installed magisk 14.4
installed magisk manager,
installed systemless xposed module from within magisk manager,
and finally installed material design xposed installer
(with reboot between each step)
and finally i have magisk root and working xposed.
If i select magisk core only mode (witch disables magisk modules) it passes safetynet and theoretically i can install OTA updates (i think xposed -systemless or not- does not pass safetynet)

ilpanos said:
I just did the following procedure:
flashed official rom with miflash,
booted to rom,
intalled second october OTA update (75mb),
booted twrp with "fastboot boot recovery.img",
and then:
installed magisk 14.4
installed magisk manager,
installed systemless xposed module from within magisk manager,
and finally installed material design xposed installer
(with reboot between each step)
and finally i have magisk root and working xposed.
If i select magisk core only mode (witch disables magisk modules) it passes safetynet and theoretically i can install OTA updates (i think xposed -systemless or not- does not pass safetynet)
Click to expand...
Click to collapse
Can you provide link all of these ?

Magisk v16 bootloop

Hi all,
Just tried to flash the latest Magisk (16.0) from TWRP on my honor 8 running B360 and am now in a a bootloop.. Nothing new fixing this but does anyone know what version of magisk will work or why this could have happened? I'm keen to get it working!
Cheers

So I've tried to flash back to an unrooted rom and must've broken something because I now cannot get into TWRP at all. I fastboot flash version 3.1.1-1 which has worked for me countless times and fastboot says it flashes fine but when I try and boot into it with power+vol up the phone goes off for a second, vibrates, pauses for another second before vibrating again and then showing the device cannot be trusted screen. Has anyone ever had this? I'm not sure what else to try here (I also tried flash stock recovery and it does the same thing)
Edit: Got TWRP back, I think my device must be on an earlier version (even though it's corrupt). In case anyone else finds this, this thread helped me https://forum.xda-developers.com/honor-8/help/please-help-boot-enter-recovery-t3660408/page3

First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.

Mumtaz77 said:
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Click to expand...
Click to collapse
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!

JoshSnitz said:
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
Click to expand...
Click to collapse
Unfortunately it didn't work - resulted in the bootloop again

Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?

xuso77 said:
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
Click to expand...
Click to collapse
Yeah, using twrp-3.1.1-1-frd.img. Phone is EMUI 5.0, android 7.0 FRD-L09C432B360
Edit: I have the AL version with dual sim that I've re-branded. Could this be causing an issue?

I don't think so, but I don't know.
Can you try to flash the last magisk developer version, or wait for another user that rebranded the honor.
Good luck!

You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.

hackslash said:
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
Click to expand...
Click to collapse
Oh, I'll give it a go. Is it more reliable to just flash through fastboot or the zip through twrp?
Edit: Both v14 and 13 gives boot loop when flashed from twrp

lost root after 5.1.9 OTA upgrade, how to get it back

Hi.
I have Magisk Manager installed and tried to upgrade from OOS 5.1.8 to 5.1.9 (full OTA update). I don't have TWRP.
I've reinstalled Magisk before the needed restart as described in https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 (worked previously),
buy I've lost root on my phone.
What's the best way to get it back?

Sometimes Magisk gets borked, and nothing but a full wipe will fix it. Has happened to me a couple of times.

Did u use "install to 2nd slot" or "patch boot image"?
BTW if u want to keep stock recovery, u can boot to TWRP and flash whatever u want.

Tell us if you're using Magisk stable ( 16.0 ) or beta ( 16.7 ). I went to beat a couple steps back with no problems. ( knock on wood ) But I've read some run into trouble with 16.7

old_fart said:
Tell us if you're using Magisk stable ( 16.0 ) or beta ( 16.7 ). I went to beat a couple steps back with no problems. ( knock on wood ) But I've read some run into trouble with 16.7
Click to expand...
Click to collapse
I had Magisk 16.7 before the OTA upgrade, but now it looks like I'm on 16.0?
Also, after trying to reinstall Magisk I don't get the Install to second slot option, just the 2 options: download zip and boot image patch
any tips?

kebq said:
I had Magisk 16.7 before the OTA upgrade, but now it looks like I'm on 16.0?
Also, after trying to reinstall Magisk I don't get the Install to second slot option, just the 2 options: download zip and boot image patch
any tips?
Click to expand...
Click to collapse
.
first tip - have a good reliable backup.
next tip - grab the beta and install it. . . if you can't find the 16.7 then use the 16.4 . because it'll update itself when you go into the app and run it . . . and good luck !

make sure in magisk manager you go to settings and select the beta channel and not the stable otherwise if you update via magisk manager youll go back to 16.0
if magisk is broken install the magisk uninstallater twrp, then flash boot.img, then go back to twrp and flash magisk - no need to flash ROM again.

Magisk 17.0 Resulted To Bootloop

I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager

HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol

Flashed uninstall magisk and than magisk 17 and all worked well.

dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back

Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.

Running 17.1 and still getting the same thing with safety net check as before
The response is invalid

HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks

From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful

it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk

Anyone able to root the Dec update?

For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).

i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me

Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?

Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.

To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.

Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.

I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).

FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?

Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.

somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.

https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC