Database Develop

[Magisk/Root/Xposed/Busybox]Huawei P9 Lite

-This methode is old but working with emui 4 Android MM (6). Not work with Android N (7).
-Xposed not work in systemless mode if your Android security patch is >= november 2016
-Try to search the last version of zip files and apk on google, the version on this tutorial is old.
Hi!
This tutorial will install Magisk, phh's superuser, xposed and busybox on your Huawei P9 lite device!
Tested on a VNS-L31C432B151 version but normally work on all VNS-L31 and VNS-L21.
Magisk will allow you to "hide" the root... not realy just hide because Magisk and phh's superuser systemless edition create the root outside the system folder!
Magisk feature for common user:
-"hide" root (PokémonGo, Androidpay, banking app, ... all work!) work with
-Magisk not only allow you to replace existing file and directories, but also support adding new files and directories into system!
-Update OTA work! (not tested by me)
For more detail visite this post: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Phh's superuser work at 100% on this device
After a lot of Xposed version tested I can say that Xposed systemless edition is by far the best for P9 lite!
DONT install busybox on system folder!
Ok let's go:
1 Update your system on last emui version and swipe data/factory reset to get a clean and untouched device!
2 Unlock your bootloader (see multiple method on this forum)
3 Install TWRP 3.0.2.0 (see multiple method on this forum)
4 Download this files: Magisk V6.zip / phh's superuser 17.zip / xposed-v86.5-sdk23-topjohnwu.zip / Magisk Manager.apk / XposedInstaller_by_dvdandroid.apk. Put all this files on your externalSD.
5 Go to TWRP recovery and flash in order [Magiskv6.zip > phh's_superuser.zip > Xposed-v.86.5.zip] also reboot your device.
6 When you are on the homescreen go reboot again.
7 Install Magisk Manager.apk and XposedInstaller.apk, then go to the playstore download and install Phh's SuperUser app AND Busybox meefik. Reboot after this step.
8 Open your setting app and allow permission SD card to Busybox.
9 Open Busybox >> settings. Remplace the path file /system/xbin/ with /data/busybox/ and check "Remplace Applets". Also go Menu Zip Archive and download this zip.
10 Go on TWRP recovery and flash the busybox zip file.
10 please perform 3 or 4 reboot
DONE!
So, please try to open yours setting app. if it appears you have done! If not, please try again this method
Now, go Magisk Manager (app) and switch root togle off, launch your protected against root app and normally work!
(Dont need reboot between switch root off/on!)(Selinux switch work, but not persist a boot)
Have fun!

Well done. Works perfect.

The are no files any more

Links are dead

deleted

Evas0r said:
Battery draining after the process...
Is this xposed fault?
Click to expand...
Click to collapse
yes u have to flash another version

Did anyone try this on Nougat/Android 7?

Alexander33 said:
Did anyone try this on Nougat/Android 7?
Click to expand...
Click to collapse
TWRP with this [RECOVERY]Revolution Recovery Android Nougat {15-12-16} Beta .9 in Nougat but anything I tried to flash failed.

Is there anything one can do to get Pokémon Go working while having all of these installed?

Alexander33 said:
Did anyone try this on Nougat/Android 7?
Click to expand...
Click to collapse
Hey, man I've tested it on my Huawei P9-LITE B370 and it all works perfectly. To flash Magisk, you need this custom recovery (https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356)

this really helped me thanks

Helped me alot. Still, post is a bit old, so what I did on b380 version:
FLASH RECOVERY twrp-3.1.1-0-venus.img
FLASH KERNEL Elite+Kernel+for+P9+Lite+CxxB3xx+v10.1.zip
ROOT with Magisk-v13.0(96f8efc).zip
INSTALL busybox archive via recovery to /sbin (for me it installed on /system/xbin, still ok.)
REBOOT after each step
Finally works ! :good:

is this Magisk work on Huawei P9?

I have Emui 5.0 and Android 7.0. I flashed everything except xposed but I still can't use Pokémon Go or Snapchat. Is it beacause i can't flash xposed? And when yes, how can I fix it?
Lg ThePrinoob

ThePrinoob said:
I have Emui 5.0 and Android 7.0. I flashed everything except xposed but I still can't use Pokémon Go or Snapchat. Is it beacause i can't flash xposed? And when yes, how can I fix it?
Lg ThePrinoob
Click to expand...
Click to collapse
flash magisk v13

simo255 said:
flash magisk v13
Click to expand...
Click to collapse
Ok, I will test it!

I installed magisk v13 and got the app but it when it check safety net it doesnt work. What should I do?

ThePrinoob said:
I installed magisk v13 and got the app but it when it check safety net it doesnt work. What should I do?
Click to expand...
Click to collapse
enable magisk hide and see if usb debugging is enabled

simo255 said:
enable magisk hide and see if usb debugging is enabled
Click to expand...
Click to collapse
Okey thank you it worked.

Hey,
If I open the camera app or snpachat I cant make any picture so I have a blackscreen. What should I do? And in youtube or Instagram I cant see videos, they dont load and I also cant hear any sound.
Sorry for my bad english.

Why my 3T stuck at oneplus logo after flashing xposed in magisk?

I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu

Somebody help me...

I am sure it has been mentioned many times in other threads and forums too.
Magisk 14+xposed seem to be incompatible.
This bootloop happened to me also. I just returned to TWRP and reflashed 13.3.
Problem solved.
Unleashed by ONEPLUS 3T rooted

Why don't flash system version of Xposed?

caryle said:
I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu
Click to expand...
Click to collapse
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.

Aneejian said:
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.
Click to expand...
Click to collapse
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?

caryle said:
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?
Click to expand...
Click to collapse
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
I've read the posts before. I just want to know if it caused by anything else.Now I'm going to flash the xposed system.

There is a better solution:
1 Get this zip file (thanks to @LarappsOfDongle)
2 Flash it by using adb sideload or adb push
3 Go to /magisk in recovery using built-in file manager if using TWRP or use Aroma
4 Delete ONLY folder with or similar name as xposed_framework_25 (be careful in TWRP you need to go into the folder first to delete it)
DON'T DELETE ANY OTHER FOLDER
I had the same issue. Tested with Xposed Framework 25 Magisk 14.0 Oxygen OS Open Beta 14 OnePlus 3T.

FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.

Didgeridoohan said:
FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.
Click to expand...
Click to collapse
Which is this 87.3 version?
And which magisk module u need to uninstall before?
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
Which is this 87.3 version?
Click to expand...
Click to collapse
The one in the Magisk repo (Downloads section in the Magisk Manager).
And which magisk module u need to uninstall before?
Click to expand...
Click to collapse
Xposed... (@topjohnwu changed the module id with version 87.2, if you don't uninstall any previous version you'll get conflicts)

Root using Magisk v14

Hello,
I just got my P10 (VTR-L29) yesterday, coming from a P8 Lite that I used to play a lot with and I already miss the adblock and the clean debloated system.
According to the new version of Magisk here, there is a new install method that works if you don't have a custom recovery like it used to be in the past. The new method modifies the boot.img via Magisk Manager, stores it in a folder and then you have to flash it with adb.
My question is: Do I have to unlock my phone in order to do that trick? Anyone else that tried something similar?

Nobody?
Maybe I'm not clear enough..
Steps to reproduce:
-install Magisk Manager 14 and use the inside app patcher
-find the patched boot.img on storage
-move the boot.img in PC storage
-use the PC in order to flash the patched boot.img
-reboot and wait
It's supposed to work that way but I don't want to unlock the bootloader,atleast for now.
Is it safe to do?

Xperias do not boot with the bootloader locked if boot.img is changed. I guess it will be the same for Huaweis.

So the only way to do that is to unlock the bootloader..seems like I have to do it lol.

Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?

Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.

Firicel69 said:
Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.
Click to expand...
Click to collapse
Already tried that (the new one for v14). Unfortunately, it didn't work.
Thank you anyway

garris_bibop said:
Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?
Click to expand...
Click to collapse
I had the same problem. Maybe my experience will help:
Open Magisk manager and check Log->Magisk. Are there any messages from MagiskHide? It should be.
Try this:
1. Open Magisk manager and disable Magisk hide.
2. Reboot
3. Open Magisk manager and enable Magisk hide.
I used commands in Terminal Emulator
Code:
su
magiskhide --disable
magiskhide --enable
At first it didn't work out but after a lot of desperate enabling/disabling and few reboots MagiskHide started to work (I couldn't determine the reason of its misbehaving).
For now I successfully pass SafetyNet checks.

BUSYBOX android 10 Miui 11

Hello ! Every time I install BusyBox from PlayStore or Magisk Repository , I go into a bootloop ... I want to try viper audio on Android 10 Miui 11 but he needs BusyBox installed ... So , how to solve this ? I have the latest global stable 11.0.3.0 / 11.0.5.0 MIUI 11

Try to install orange fox recovey -> reinstall magisk -> install busybox from magisk. I have no bootloop when install busybox from magisk. If you bootloop when magisk module install, you easy delete module from orangefox recovey. Sorry for my bad english

mrback007 said:
Try to install orange fox recovey -> reinstall magisk -> install busybox from magisk. I have no bootloop when install busybox from magisk. If you bootloop when magisk module install, you easy delete module from orangefox recovey. Sorry for my bad english
Click to expand...
Click to collapse
Are you sure you don't have bootloop on the last MIUI 11 EEA stable 11.0.5.0 ? I tried 3 times ...

ManDone.vRs said:
Are you sure you don't have bootloop on the last MIUI 11 EEA stable 11.0.5.0 ? I tried 3 times ...
Click to expand...
Click to collapse
Your phone bootloop when install magisk or busybox ?? If bootloop when install magisk try to "format data" not " wipe data" . note " format data" will delete all internal storage
I don't use EEA but every rom i use eg : xiaomi eu, miuimix, lineage os,PE ... No bootloop when install busybox, just bootloop when install magisk

mrback007 said:
Your phone bootloop when install magisk or busybox ?? If bootloop when install magisk try to "format data" not " wipe data" . note " format data" will delete all internal storage
I don't use EEA but every rom i use eg : xiaomi eu, miuimix, lineage os,PE ... No bootloop when install busybox, just bootloop when install magisk
Click to expand...
Click to collapse
It's bootloop after flashing or install BusyBox . The last version of miui 11 and Android 10

same case on me
im on miui 12 android 10, global stable 12.0.1.0, waiting for solution, because i want instal v4a like before when im on miui 11

ManDone.vRs said:
It's bootloop after flashing or install BusyBox . The last version of miui 11 and Android 10
Click to expand...
Click to collapse
This is SAR. Do not install BusyBox app but BusyBox (systemless) Magisk Module from Magisk Manager

zgfg said:
This is SAR. Do not install BusyBox app but BusyBox (systemless) Magisk Module from Magisk Manager
Click to expand...
Click to collapse
That`s works on all SAR devices or not? I have Samsung SM-T510 (all new Samsung`s going with system-as-root) and root it through Magisk app like in official guide from John Wu for Sams devices, but i have any doubts about installing Magisk modules on modified (but still commonly stock) ROM.

vlrgamaley said:
That`s works on all SAR devices or not? I have Samsung SM-T510 (all new Samsung`s going with system-as-root) and root it through Magisk app like in official guide from John Wu for Sams devices, but i have any doubts about installing Magisk modules on modified (but still commonly stock) ROM.
Click to expand...
Click to collapse
Unfortunately, there is no such thing - "works on all devices" or things like that.
Nobody can guarantee you in advance (if not willing to test yourself, afraid of nuclear blast or something, then don't root your phone )
There are differences between vendors, Android version, etc, specially who knows in advance what you might have in your custom ROM xxx on the device yyy and would something work or not
However, if SAR is read only, then any BusyBox installation (like older apps, maybe older modules) that attempt.to write directly to /system will fail.
Therefore suggestion was to use the given BB module, that uses the systemless mechanism provided by Magisk - in that case it SHOULD work no matter if your SAR is read-only or not
Plus, you just later disable the module and reboot, and BB is gone.
Similarly for any other systemless module and all their artefacts they 'install' to the System - hence, the systemless changes are much more 'secure' than old methods that attempt to make hard changes directly to the System (if something ever goes wrong you then have to reinstall the ROM or manually search and revert changes left by those apps)
If you are you are not familiar with the systemless concept, wether your SAR is read-only or not, etc - please google

Magisk installed. But doesn't work. 24.3

So i have latest stable branch and when i patched my boot.img. Install them from TWRP.
In app they appears like
Magisk
Installed N/A
Zygisk No
Ramdisk Yes
Application
Availible 24.3 (24300) (27)
Installed 24.3 (24300)
Package name com.topjohnwu.magisk
Have finger scanner on. Data encrypted in TWRP.
I DO NOT WANTED TO ERASE DATA. FUСK IT. REALLY.
I spend all day to setup phone after flashing and that method just kill me.
I have no idea how to fix it.
Phone: Blackview 8000 pro (Latest official firmware: 8.0 Oreo)

May I ask why you don't just rename the apk to zip and flash itnin twrp?

jamboss said:
May I ask why you don't just rename the apk to zip and flash itnin twrp?
Click to expand...
Click to collapse
I made it in end. Read from manual in end. That they fault why they pull that method in very end. Anyways flashed, and they start works.

Great, glad you got it sorted.