Database Users

[GUIDE] [F3111] HOW TO Install Magisk on Xperia XA

Steps:
1. Download Magisk V11.1 & uninstaller
2. Root device (use @rrvuhpg root guide)
3. Download and flash Systemless SuperSU
4. Reboot and fully unroot device (don't restore stock boot image)
5. Reboot
6. Reboot into recovery
7. Flash Magisk & reboot
8. Wait for device to reboot fully (it takes a long, long time)
9. Download Magisk Manager from Play Store
10. If root is there, then you're done
Alternate Method:
1. Root Device (use @rrvuhpg root guide)
2. Download and flash Systemless SuperSU
3. Reboot and install Magisk Manager from Play Store
4. Open Magisk Manager and go onto the install tab
5. Press "detect" on the boot image location section and press "Magiskify" (I kept both advanced options unchecked)
6. Once flashed and rebooted, you're done.
Notes:
1. Rebooting after flashing Magisk takes ages, if there is a problem with booting then just flash the Magisk uninstaller. Just try to wait at least 10 minutes for the reboot after flashing Magisk, just don't crap yourself and uninstall the Magisk.
If you have questions or need help, just ask.

is this for single or dual sim XA??

caosugai said:
is this for single or dual sim XA??
Click to expand...
Click to collapse
For all XA and Ultra

rrvuhpg said:
For all XA and Ultra
Click to expand...
Click to collapse
Did it work for you then?

BadmanBristow said:
Did it work for you then?
Click to expand...
Click to collapse
No problem for me on F3112 with Magisk 11.1 and SuperSu 2.79 on 33.2.B.3.105 firmware. Only SafetyNet fail (CTS profil mismatch).

rrvuhpg said:
No problem for me on F3112 with Magisk 11.1 and SuperSu 2.79 on 33.2.B.3.105 firmware. Only SafetyNet fail (CTS profil mismatch).
Click to expand...
Click to collapse
Use MagiskSU instead, fully unroot device with SuperSU but don't restore the boot.img etc. Go to recovery and use the Magisk uninstaller then reflash Magisk 11.1 and if you unrooted, then it will install MagiskSU. It is Magisk's new official root

rrvuhpg said:
No problem for me on F3112 with Magisk 11.1 and SuperSu 2.79 on 33.2.B.3.105 firmware. Only SafetyNet fail (CTS profil mismatch).
Click to expand...
Click to collapse
Also Systemless xposed causes safety net fail and you need to activate Magisk hide in the settings as well

BadmanBristow said:
Also Systemless xposed causes safety net fail and you need to activate Magisk hide in the settings as well
Click to expand...
Click to collapse
And selinuxmode needs to be enforcing but Magisk takes care of that itself so don't worry, just double check it's enforcing, Magisk will turn it permissive itself only when needed

BadmanBristow said:
And selinuxmode needs to be enforcing but Magisk takes care of that itself so don't worry, just double check it's enforcing, Magisk will turn it permissive itself only when needed
Click to expand...
Click to collapse
Thank you for your tips but XA is not my daily phone anymore, now I have a Oneplus3 and XA is just used as test/dev unit. I hope it will help other users.

Magisk should help with maintaining root after the latest and future Xperia XA updates (most likely will work with Nougat update too)

Android Pay
does this let you use android pay

jbenitez821 said:
does this let you use android pay
Click to expand...
Click to collapse
It does, but if you use systemless xposed, you will need to disable it and then it will work.

Thank you very much for this guide.

Can't I use just Magisk installer without unrooting the rom? If I'm not wrong Magisk has is own root manager

I tryed to install Camera 60fps Recording Module but i got error the zip is stored in : intenal storage ....

Is this safety net important to have it in green to pass this CTS ? I have done method 2. Magisk manager form store and then I installed Magisk 12. In installation panel when I tap detect it detecs (auto) mmcblk. Is it all ? Does it work ?

Where can I find the Systemless SuperSU?

I have been trying to change to Magisk with this guide but it failed in the 1st method, the 2nd one gives the root with super su but i wanted to use Magisk alone, so i have been researching and by flashing the stock boot.img (i used the one provided in the thread "Stock kernels built from sources") Magisk was installed and worked except for the SafetyNet. Do someone passes SafetyNet or have a suggestion?

Veniak04 said:
I have been trying to change to Magisk with this guide but it failed in the 1st method, the 2nd one gives the root with super su but i wanted to use Magisk alone, so i have been researching and by flashing the stock boot.img (i used the one provided in the thread "Stock kernels built from sources") Magisk was installed and worked except for the SafetyNet. Do someone passes SafetyNet or have a suggestion?
Click to expand...
Click to collapse
To pass the Safetynet check the only way is to use encrypted partition but you will lose the ability to mount/backup the /data partition with TWRP.

rrvuhpg said:
To pass the Safetynet check the only way is to use encrypted partition but you will lose the ability to mount/backup the /data partition with TWRP.
Click to expand...
Click to collapse
How can i encrypt it and why does it is an issue? I only want to have my phone rooted with Magisk passing SafetyNet

MAGISKSU for Magisk users

So as we all know magisk does not root nonrooted or supersu rooted devices (atleast not my devices) so here is simple method to gain MagiskSU Root access and possibly hide your root.
Note: i will use phh's superuser which was used in magisk before.
COMPATIBILITY:
ANDROID 7.x -- Not confirmed
ANDROID 6.0.1 -- Confirmedly working!
1) DOWNLOAD PHH'S SUPERUSER https://superuser.phh.me/
2) BOOT INTO RECOVERY AND FLASH DOWNLOADED ROOT ZIP AND MAGISK IF NOT FLASHED ALREADY
3) REBOOT AND ENJOY
IMAGES:

MagiskSU works just fine without flashing anything else for me

Opticuhl said:
MagiskSU works just fine without flashing anything else for me
Click to expand...
Click to collapse
Glad to hear it! For me it never did

Wizardlysense said:
So as we all know magisk does not root nonrooted or supersu rooted devices (atleast not my devices) so here is simple method to gain MagiskSU Root access and possibly hide your root.
Note: i will use phh's superuser which was used in magisk before.
COMPATIBILITY:
ANDROID 7.x -- Not confirmed
ANDROID 6.0.1 -- Confirmedly working!
1) DOWNLOAD PHH'S SUPERUSER https://superuser.phh.me/
2) BOOT INTO RECOVERY AND FLASH DOWNLOADED ROOT ZIP AND MAGISK IF NOT FLASHED ALREADY
3) REBOOT AND ENJOY
IMAGES:
Click to expand...
Click to collapse
Trying to get this working on my HTC 10 so flash the phh then v12. 0 which is now available? Does anything else need to be done??
I've downgraded to mm so I can get half life 2 to work.
Nice having xposed again.
Sent from my KFGIWI using XDA-Developers Legacy app

dladz said:
Trying to get this working on my HTC 10 so flash the phh then v12. 0 which is now available? Does anything else need to be done??
I've downgraded to mm so I can get half life 2 to work.
Nice having xposed again.
Click to expand...
Click to collapse
Flash magisk 12.0 then phh superuser

Wizardlysense said:
Flash magisk 12.0 then phh superuser
Click to expand...
Click to collapse
I have.
Will try again now.

Wizardlysense said:
Flash magisk 12.0 then phh superuser
Click to expand...
Click to collapse
Ok so this is not the correct procedure for getting Magisk to work, this is exactly how it's done in my case at least.
1. Flash a rom of your choice ( in my case it was viper rom on the HTC 10, rooted with SuperSU, I have an international unlocked device with S-Off)
2. Extract the boot.img from your ROM ( in my case it was in the root of the rom's zip file)
3. Copy the boot.img to your Fastboot folder on your computer.
4. Install Magisk Manager and download Magisk 12.0 zip to your phone.
5. Reboot to download mode and then: fastboot flash boot boot.img allow it to flash, press power to come out.
6. Without rebooting, boot to recovery and flash the Magisk 12.0 zip.
7. Reboot and check the 3 sections to see if MagiskSU has been locked in, no warning should come up when activating Magisk hide.
Done.

Magisk on Mate 9 Pro

Is someone had more luck with Magisk than me ?? I have a rooted LON-L29C432B225. Was trying Magisk 13.3 but without luck. Phone restarts automatically during magisk installation through twrp.

I have finaly made it Magisk is working without problems on Mate 9 Pro (LON-L29C432B225).
1. Install latest twrp recovery - https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
2. Unroot rom, easy way i to download boot.img and flash by fastboot flash boot boot.img (https://www.dropbox.com/s/sj5su702r8omp2u/BOOT.img?dl=0)
3. Thanks to @ante0 (https://forum.xda-developers.com/member.php?u=2247733), he made a modified magisk package - https://mega.nz/#!QhMmRDgC!c3UqYIoaGtsekmJbWoP5x90spHbXVhircmmA_68s3pY
4. Flash magisk in twrp
5. After reboot you receive info about magisk update to 13.3. Mark in magisk manager settings "keep force encryption" and allow to update.
6. After next reboot you shuld have working magisk and SafetyNet status green
I hope it will help someone

On AL00 mate 9, followed the same procedure except downloading the boot.img as restored by huawei eRecovery, only unlocked the bootloader and didn't do anything else. Can install 13.2 modified version but safetynet fail, update to 13.3 with keep force encryption then bootloop. Checked the magisk log nothing seems wrong when can boot. Root works fine. Any help? Thanks

Guys any updates on Magisk v14 with xposed on our phone? fw B225

Magisk V17 - V17.1

Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.

Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.

iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
I'll try right away.

iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thank you bro, I followed same steps however, I got a bootloop ;(

MaZeNsMz said:
Thank you bro, I followed same steps however, I got a bootloop ;(
Click to expand...
Click to collapse
I can't say what else would help sorry, those are the exact steps I followed and they worked.
Perhaps you could post in the Magisk part of the forums with some info about your device and see if someone could help.

MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
This is a magisk issue and shouldn't be posted here
Sent from my LG-H910 using XDA Labs

I had the same problem till I went to twrp recovery and flashed the zip that magisk downloaded and it works great. Only problem left on the side is trying to get Xposed to work again through the new magisk on H918 Super Rom, it's not working ATM but I think it's fixable somehow I guess. Magisk is effecting all phones, not just V20 btw.
Check out the video about the API and safetynet by the YouTuber HighOnAndroid. That video let's u know what's up with magisk the day before new magisk update came.

Is it possible that someone backup and share with me boot partition, and from my side I recover it ?!

I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?

I was able to directly install Magisk 17.1 from Magisk itself without issues.

SebTech33 said:
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
Click to expand...
Click to collapse
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0

KawaiiNek0 said:
I was able to directly install Magisk 17.1 from Magisk itself without issues.
Click to expand...
Click to collapse
Very locky,
I did the same here by I end up with a nice boot loop

MaZeNsMz said:
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
Click to expand...
Click to collapse
Have you tried another kernel?

Anyone could test sixaxis compatibility checker?
(free on store)
Only on h990ds. 910 and other never were affected by this problem with previous magisk.
Dont know if v17 solved this problem.
Thanks

SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
I'll try today, do you recommend any kernel?

SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
Tried D.O.T.S and failed, bootloop
I am thinking if someone can backup the boot and share it with us. So we can recover it
Regards..

Has anyone found a way to make 17.1 work on the H990DS? It took me several flashes to get it to boot but after a couple restarts it started bootlooping again so I had to downgrade to 16 and 16 works just fine

Just stay on v16 until they can work the bugs out with v17 -- you aren't gaining anything by going to v17.
-- Brian

iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thanks, that did the trick for me on lg h910r

MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
Note 26.10.2018 :
I upgraded to Oreo V8.0 from here and everything is fine now

[QUESTION] Update from OOS 10.0.1 to 10.3.0

Happy new year to all you merry people
Going to update my international OP6T from 10.0.1 to 10.3.0. I have TWRP, cutom kernel and Magisk with several modules. I don't care about TWRP, only need Magisk and custom kernel. My plan is:
Clean flash full 10.3.0 from here
reboot to bootloader
boot TWRP, install magisk, ElementalX kernel
reboot to OS.
Is it a correct way or will it brick the phone? Maybe omebody can suggest a better way?
Thanks in advance

It should work. Tho you can flash Magisk from Magisk Manager. There is an option to flash to Other slot after an OTA.

DarthVader said:
It should work. Tho you can flash Magisk from Magisk Manager. There is an option to flash to Other slot after an OTA.
Click to expand...
Click to collapse
So just install OTA, install Magisk to another slot and reboot? Should I uninstall all Magisk modules first?

BesoC said:
So just install OTA, install Magisk to another slot and reboot? Should I uninstall all Magisk modules first?
Click to expand...
Click to collapse
Gosh...
The official way to do it is always the same, no need to ask at every update how to do it
Flash OTA local update
Don't reboot
From Magisk Manager flash latest twrp as a module if you want twrp
Don't reboot
From Magisk Manager install Magisk on other slot
Reboot
That's the official (cf Magisk GitHub) way to do it. Period. Do what you want with Magisk modules only a very few of them can do harm. I don't touch them. And don't uninstall Magisk before OTA it's useless on our phone