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.

Magic v11 installation question

Hi, do i need install systemless SuperSU always in twrp before install magisk v11 if I want use new MagiskSU instead??
If I try install Magisk v11 with superSU uninstalled and phone unrooted TWRP give me error and installation fails and if I install superSU and after Magisk v11, Magisk manager say system is using SuperSU instead MagiskSU. How do I install Magisk with MagiskSU??
I have Samsung Galaxy S4 with optimized LineageOS 14.1

Read the pinned Magisk thread...
Unroot again using unSu by osm0sis (Google) before flashing magisk

Installation Instructions
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
Click to expand...
Click to collapse
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Code:
! SU image mount failed...
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
[B]Updater process ended with ERROR: 1
Error installing zip file 'sdcard/Download/Magisk v11.1/Magisk-v11.1.zip[/B]

dhaern said:
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Click to expand...
Click to collapse
You need to FULLY unflash superSU using the zip that the other person told you to google.

PartyPlease said:
You need to FULLY unflash superSU using the zip that the other person told you to google.
Click to expand...
Click to collapse
Ok I will try unflash with the zip, I was using unroot inside superSU menu but installation instructions dont say nothing about the unflash with an extrenal script

dhaern said:
Ok I will try unflash with the zip, I was using unroot inside superSU menu.
Click to expand...
Click to collapse
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.

Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.

PartyPlease said:
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Click to expand...
Click to collapse
ahh, this would explain why my boot.img was not the same after "unrooting"! thanks for clearing this up for me...

dhaern said:
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
Click to expand...
Click to collapse
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.

vicky_ag said:
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
Click to expand...
Click to collapse
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.

dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks but doesn't seem to work for me.

dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks for this hint; got my build "passed" now appreciate it

What settings are you guys using in Magisk? I have disabled BusyBox, enabled Magisk Hide and systemless hosts. Superuser options are Access to "Apps and ADB" and Automatic Response set to prompt

I'm still having an issue installing Magisk on my phone with RAMROM V10. It gives me an ERROR 1.
It has been suggested that I should re-flash my boot.img with TWRP following the instruction:
Place your BOOT.img on your sdcard
Reboot into TWRP recovery
Tap "Install"
In the bottom right corner tap "Install Image"
Select your BOOT.img
Select the Boot Partition, then swipe to confirm Flash
However, when I follow the step, my TWRP cannot seem to find BOOT.IMG in my SD Card (I know it is there). What did I do wrong? Can anyone help?

i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files

sm00th4f3 said:
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
Click to expand...
Click to collapse
FIY: Flashing regular boot.img files works just fine with "Install Image" in TWRP (of course, YMMV, depending on your device).

LineageOS Viper4Android

Did anyone of you got Viper4Android working on the unified builds of LineageOS for the 3T? And if so could you explain how? I tried the flashable zips of Viper4Arise but the driver was unsupported everytime and when i installed the Viper apk, installed the drivers and rebooted the app asked me again to install drivers and so on.
Thanks in advance

mittey68 said:
Did anyone of you got Viper4Android working on the unified builds of LineageOS for the 3T? And if so could you explain how? I tried the flashable zips of Viper4Arise but the driver was unsupported everytime and when i installed the Viper apk, installed the drivers and rebooted the app asked me again to install drivers and so on.
Thanks in advance
Click to expand...
Click to collapse
Install Magisk as your root solution, not SuperSU and install the module for Viper from the "downloads" section of the Magisk Manager (you will need to update Magisk Manager from play store). Reboot. After reboot, get a root file explorer and follow the instructions here: https://forum.xda-developers.com/oneplus-3t/themes/v4a-fix-processing-using-magisk-t3572819
Reboot Again. Then download the official Viper APK from: http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip (official link is from http://vipersaudio.com/blog/?page_id=48) and install it.
Done
I would clean install your rom to get rid of any existing system installs of Viper4arise or similar though. Dirty Flash should also work. @mittey68

manor7777 said:
Install Magisk as your root solution, not SuperSU and install the module for Viper from the "downloads" section of the Magisk Manager (you will need to update Magisk Manager from play store). Reboot. After reboot, get a root file explorer and follow the instructions here: https://forum.xda-developers.com/oneplus-3t/themes/v4a-fix-processing-using-magisk-t3572819
Reboot Again. Then download the official Viper APK from: http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip (official link is from http://vipersaudio.com/blog/?page_id=48) and install it.
Done
I would clean install your rom to get rid of any existing system installs of Viper4arise or similar though. Dirty Flash should also work. @mittey68
Click to expand...
Click to collapse
Worked! Thanks man

mittey68 said:
Worked! Thanks man
Click to expand...
Click to collapse
Anytime! Can't take credit for the original find though

How to root Dr Ketan's Latest Nougat Rom N10 for Note 5?

@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?

newuxtreme said:
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
Click to expand...
Click to collapse
I thought Dr. Ketan's N10 ROM was pre-rooted with either Magisk or SuperSU. Did you not have this option in the AROMA Installer? If not, here is some help..
I personally recommend Magisk for root. It's just as easy to use Magisk over SuperSU. Each root solution has its own dedicated app as well. To root with Magisk you will need the latest root zip which is V14.0 along with the latest Magisk Manager apk.
You can download the latest Magisk Manager apk and the latest Magisk V14.0 root zip from the link below...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Here you can read and learn all about Magisk too. Once you download both the root zip and the apk, transfer both to your internal storage.
Next, download the no_verity_opt_encrypt_5.1 zip from here...and transfer it to your internal storage.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
(Its the second link from the bottom in the list)
Easy steps to root your device with Magisk..
Boot to TWRP Recovery
Select Backup and put a check in each box. That way if anything goes wrong you can restore the backup and have a working device.
Next, select WIPE - Advanced WIPE - Check both caches
Swipe to wipe both caches
Next, select INSTALL
Navigate to where you saved the root zip and select the zip.
Swipe to flash the zip
Click on the box to wipe the caches
Now, just in case, flash the no_verity_opt_encrypt_5.1 zip that you downloaded earlier.
Reboot your device. Once booted up, install the Magisk Manager apk. It will install as a normal app. Make sure you have enabled "unknown sources" in Settings - Lock Screen and Security so you can install apps outside of the Play Store.
Open the Magisk Manager app and set it up to your preference. It's very easy to use.
If you run into any issues don't hesitate to ask questions.
Good luck and happy flashing!
Sent from my Samsung SM-G955U using XDA Labs

How do I upgrade from Magisk 20.4 to 22.0?

Device: Samsung Galaxy On7
Android: 6.0.1
I have Magisk Manager 8.0.7 and Magisk 20.4 installed on my device. I went to the GitHub repo and found that the app and the zip have been combined in Magisk 22.0. Fine. But how do I upgrade to v22.0? When I open the app, it asks me to upgrade the app first. Okay, I do that. When I open the upgraded app, it can no longer find Magisk. I click on "Install" beside Magisk, choose Direct Install, and then it gives me an error: Device signature invalid.
Any help is appreciated.

Wrichik Basu said:
Device: Samsung Galaxy On7
Android: 6.0.1
I have Magisk Manager 8.0.7 and Magisk 20.4 installed on my device. I went to the GitHub repo and found that the app and the zip have been combined in Magisk 22.0. Fine. But how do I upgrade to v22.0? When I open the app, it asks me to upgrade the app first. Okay, I do that. When I open the upgraded app, it can no longer find Magisk. I click on "Install" beside Magisk, choose Direct Install, and then it gives me an error: Device signature invalid.
Any help is appreciated.
Click to expand...
Click to collapse
if you have a custom recovery, change the magisk.apk file to.zip so it would be magisk.xx.zip then just flash it via twrp or whatever you have

xHvlios said:
if you have a custom recovery, change the magisk.apk file to.zip so it would be magisk.xx.zip then just flash it via twrp or whatever you have
Click to expand...
Click to collapse
Okay. Do I leave the old Manager as it is, or should I uninstall it before I flash the zip from TWRP?

Wrichik Basu said:
Okay. Do I leave the old Manager as it is, or should I uninstall it before I flash the zip from TWRP?
Click to expand...
Click to collapse
I think it will update it, so just flash the new one