Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting and Unroot Huawei P8 GRA-xxx Marshmallow (Android 6) [All Stock-Firmwares with EMUI4.0.1]
For newer Firmwares use following Guide: https://forum.xda-developers.com/showpost.php?p=75460388&postcount=323
Note: DONT FLASH SUPERSU OVER EXISTING ROOT - SINCE SUPERSU 2.82 IT IS REQUIRED TO UNROOT YOUR PHONE BEFORE USING NEWER VERSION!
SuperSU-v2.82-SR5-permissive.zip by Tecalote: https://www.androidfilehost.com/?fid=962187416754458671 MD5: b168a88bc815d3fac521ace97402a949
It enables init.d and SELinux Permissive (required for installing several mods like Viper4Android etc...)
NEW TWRP released by @AD2076 : https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img.html
This new method should work on all types of GRA (GRA-L09-TL00-CL00-UL00-UL10-TL10-CL10) for newer Firmwares from 2017 on!
For Unroot you can do it directly from SuperSU App - with restoring the boot.img (SuperSU App ask you, answer with YES) - or alternative you can flash UnSU Script with TWRP:
http://forum.xda-developers.com/showpost.php?p=63615067
If you flash unsu script - you must restore your original unmodified boot.img from TWRP Backup! This make sure you can boot straight to system after Unroot.
If you flash instead boot.img extracted from update.app you cannot boot to system before installing EMUI Recovery and doing Factoryreset.
But it is possible to Root your Phone directly after flashing boot.img to BOOT
Restoring boot.img is required after Unroot in every case! A) If you like to stay unrooted and B) if you want to Root with new Version of SuperSU. If you want Root with new SuperSU, you must restore original boot.img. After you have restored it from TWRP Backup or flashed it with adb in Fastboot Mode, you can Root directly after restoring without boot to system before.
If you cannot restore boot.img, because you have no TWRP Backup from Boot, you can download the Firmware for your build Number (Settings/About Phone) from here:
http://pro-teammt.ru/firmware-database/?firmware_model=GRA&firmware_page=0
With following Tool you can extract boot.img from UPDATE.APP - Huawei Update Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Unlocked Bootloader required
Unlocked Bootloader:
If your Bootloader is locked install the App Huawei-ID on your Phone. On newer Firmwares, the Huawei-ID App is already preinstalled.
But anyway update it to this version: https://www.androidfilehost.com/?fid=385035244224383206
After you must visit website for login and requesting the unlock-code. Visit: http://emui.huawei.com/en/plugin/hwdownload/download and click: Unlock Bootloader.
Make an Account or Login with your Huawei-ID, click again: Unlock Bootloader. Fill out form - you can find all information in Settings "About the Phone" and "Status" - for the Product-ID use dialer ( *#*#1357946#*#* ). Submit information and you receive the Unlock Code.
- On your phone activate the developer options (Settings "About the phone" press several times consecutively the "Build-Number")
- In developer options activate "USB-Debugging"
- In Settings "Security" activate "Unknown Sources" and HiSuite HDB accept
- install the latest HiSuite (from Huawei) on your PC - Download: http://consumer.huawei.com/minisite/HiSuite_en/index.html
- start HiSuite and connect your Phone with the USB-Cable with your PC. You will receive a fingerprint question on your Phone, acitvate "Always" and "Yes"
- accept also the installing of HiSuite on your Phone. As soon the drivers are installed and your phone is succesful connected, close HiSuite (even in the background).
- unzipp "Minimal ADB + Fastboot", install it on your PC - Download: https://www.androidfilehost.com/?fid=385035244224386526
- (the path will be C:\Program Files (x86)\Minimal ADB and Fastboot) - after open the Program as Administrator
- tap: adb devices (your device must listed with ID)
- tap: adb reboot bootloader (Phone restart in Fastboot-Mode) You will see, your bootloader is locked
- wait until PC installs additional drivers, after:
- tap: fastboot devices (your device must listed with ID)
- tap: fastboot oem unlock YOUR16DIGITCODE (which you have received from Huawei) - after unlock tap: fastboot reboot
If you have problems to execute fastboot-commands and you see just: "Waiting for any devices" - or if you have trouble with hardware-buttons read following information: http://forum.xda-developers.com/showpost.php?p=69440645&postcount=129
Old methods (2016) - not reccomended for newer Firmwares (2017..)
It is no more possible to Root Huawei Firmware up to EMUI 4.01 with newer Versions of SuperSU (current stable 2.78) neither with the Force Systemless Command! Dont try it, because SuperSU will destroy the original boot.img of the Firmware - See Screenshot 1. You can flash the zip but your phone would not boot and staying on the Rescue-Screen of the Bootloader.... That´s why I maked this Thread!
All methods updated 13.10.2016 - everything works now! .
For systemless rooting (like my method A) you can also use the SRKToolHuawei 2.0 by @somboons
- Download: https://www.androidfilehost.com/?fid=529152257862664925 - Thread: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Before you going to root your phone make a full Nandroid Backup (all shown Partitions) with TWRP - if something goes wrong you can restore your backup.
Thread for German Speakers GRA-L09: http://www.android-hilfe.de/thema/huawei-p8-b380-root-anleitung.797464/
Requirements:
1) Unlocked Bootloader:
If your Bootloader is locked install the App Huawei-ID on your Phone. On newer Firmwares, the Huawei-ID App is already preinstalled.
But anyway update it to this version: https://www.androidfilehost.com/?fid=385035244224383206
After you must visit website for login and requesting the unlock-code. Visit: http://emui.huawei.com/en/plugin/hwdownload/download and click: Unlock Bootloader.
Make an Account or Login with your Huawei-ID, click again: Unlock Bootloader. Fill out form - you can find all information in Settings "About the Phone" and "Status" - for the Product-ID use dialer ( *#*#1357946#*#* ). Submit information and you receive the Unlock Code.
- On your phone activate the developer options (Settings "About the phone" press several times consecutively the "Build-Number")
- In developer options activate "USB-Debugging"
- In Settings "Security" activate "Unknown Sources" and HiSuite HDB accept
- install the latest HiSuite (from Huawei) on your PC - Download: http://consumer.huawei.com/minisite/HiSuite_en/index.html
- start HiSuite and connect your Phone with the USB-Cable with your PC. You will receive a fingerprint question on your Phone, acitvate "Always" and "Yes"
- accept also the installing of HiSuite on your Phone. As soon the drivers are installed and your phone is succesful connected, close HiSuite (even in the background).
- unzipp "Minimal ADB + Fastboot", install it on your PC - Download: https://www.androidfilehost.com/?fid=385035244224386526
- (the path will be C:\Program Files (x86)\Minimal ADB and Fastboot) - after open the Program as Administrator
- tap: adb devices (your device must listed with ID)
- tap: adb reboot bootloader (Phone restart in Fastboot-Mode) You will see, your bootloader is locked
- wait until PC installs additional drivers, after:
- tap: fastboot devices (your device must listed with ID)
- tap: fastboot oem unlock YOUR16DIGITCODE (which you have received from Huawei) - after unlock tap: fastboot reboot
If you have problems to execute fastboot-commands and you see just: "Waiting for any devices" - or if you have trouble with hardware-buttons read following information: http://forum.xda-developers.com/showpost.php?p=69440645&postcount=129
2) There is a new TWRP released by KangV from the Huawei Rom Team (HRT) v. 3.0.2 - multilingual. Download: https://www.androidfilehost.com/?fid=529152257862681510
- rename the .img to "TWRP" (TWRP.img) and flash it with ADB.
- first store the TWRlP.img in C:\Program Files (x86)\Minimal ADB and Fastboot, after open the Program (Phone must be connected with USB to PC)
- tap: adb devices (your device must listed with ID)
- tap: adb reboot bootloader (Phone restart in Fastboot-Mode - you will see, your bootloader is unlocked now)
- tap: fastboot flash recovery TWRP.img
If the flashing of the Recovery is succesfully done - disconnect your Phone from USB!
- press the Vol+ button first (staying on Vol+) and simultaneously press the Power Button
- wait until the phone reboot - in the moment you see the Huawei Logo skip pressing the Power Button but stay on Vol+ until you are succesfully bootet to TWRP
- TWRP ask you by the first start for root access "Allow to modify system partion" - swype to confirm "yes"
- go to button "Backup", select your external Storage and make a complete Nandroid Backup of all shown partititions
- after you can Root your Phone now - see description
Note: If you make something wrong booting first time to TWRP and the Phone reboot to system instead of TWRP, Stock-Recovery will be reflashed and you must flash TWRP again with ADB
A) Rooting in systemless Mode (by maintaining the original Stock-Kernel)
Note: This kind of rooting your phone is for for normal use (Root-Explorer, Root-Apps) but not for Hardliner-Mods
Your TWRP should always have write permissions, if it ask you swype to confirm this! If it don`t have, you can enable this in the Mount button (disable system partition read only)
1.) Download SuperSU with your Browser (not with Downloadmanager) 2.67: https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip?retrieve_file=1
- or download the file from the attached file below in OP and place SuperSU 2.67 on the external SD
2.) Boot to TWRP and make a complete Nandroid Backup first (if you dont have it already)
3.) In TWRP go to the Advanced button and use the Terminal.
On the first screen tap on the ok button and after write following Force Systemless Command:
echo SYSTEMLESS=true>>/data/.supersu
and quit this with the ok tab
4.) Navigate back to the main menu and use the Install button
5.) Navigate to the location of the placed SuperSU 2.67
6.) Swype to confirm flash - after use: Reboot
7.) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
8.) P8 reboots now 2 times and rebooted finaly to system.
9.) Open the SuperSU App (it will be on an empty site of your home) - you have now systemless Root
10.) Open Playstore an Update the SuperSU and after say yes to Update the Binary.
11.) The Phone must be restarted and you are up-do-date with the Root.
Uninstall this kind of Root:
If you want to unroot your Phone and you have used method A, do following:
1) If you have Xposed Framework installed - uninstall it with the uninstaller.zip (matching your phone) in TWRP - directly after you must Wipe Cache and Dalvik - next step: reboot your phone.
2) If you have BusyBox installed - uninstall it with BusyBox-Cleaner.zip in TWRP - Download: https://www.androidfilehost.com/?fid=24591000424941581
3) Reboot Phone open SuperSU and tap "complete Unroot"
4) If SuperSU ask you to restore your original Boot Image - say yes!
5) If the phone reboot automatically Unroot is ready - check it with Root Checker
6) If the phone dont reboot automatically, boot into TWRP and:
7) flash unsu.zip - Download: http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893 - reboot your Phone and Unroot is ready.
8) If the Download-Link of unsu.zip has changed, because it gets updates - you find it on this site: http://forum.xda-developers.com/showpost.php?p=63615067
B) Rooting in SYSTEM-Mode (by using modified Stock-Kernel made for Rooting with SuperSU)
1.) Download SuperSU - current version 2.79 Stable (with Browser, not with Downloadmanager): https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip?retrieve_file=1- it is the original one from Chainfire, not CCMT
2.) Download the Kernel, which allow you to Root: https://www.androidfilehost.com/?fid=385035244224383592
3.) Place both zips on the external SD
4.) Reboot to TWRP Recovery
5.) Make a comlete Nandroid Backup
6.) Navigate back to the main menu
7.) Use: Install - and navigate to the place of the Kernel-for-Root-Stock-MM.zip
8.) Swype to confirm flashing the Kernel-for-Root-Stock-MM.zip
9.) Directly after this flash navigate back to the main menu
10.) Use: Install - navigate to SuperSU.zip
11.) Swype to confirm flashing SuperSU - after use: Reboot
12.) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
13.) P8 reboots one times directly to the system
14 Open the SuperSU App (it will be on an empty site of your home) - you have now Root in the System with the latest stable SuperSU
Unroot this Installation of Root in System-Mode:
1) If you have Xposed Framework installed - uninstall it with the uninstaller.zip (matching your phone) in TWRP - directly after you must Wipe Cache and Dalvik - next step: reboot your phone.
2) If you have BusyBox installed - uninstall it with BusyBox-Cleaner.zip in TWRP - Download: https://www.androidfilehost.com/?fid=24591000424941581
3) Reboot Phone open SuperSU and tap "complete Unroot" - Needs some seconds, after:
4) flash unsu.zip - Download: http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893 - reboot your Phone and Unroot is ready.
5) If the Download-Link of unsu.zip has changed, because it gets updates - you find it on this site: http://forum.xda-developers.com/showpost.php?p=63615067
6) Reboot your Phone, and if
7) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
8) After Reboot check it with a Root Checker - Your devices is not Rooted!
C) Systemless Rooting (by using modified Stock-Kernel made for Rooting with SuperSU)
Note: This is the only kind of Root to install the Systemless Xposed Framework!
This Thread does not officially Support the issue "how do hide Root" . Please use other Threads made for this. But you're invited to post ideas and solutions for this issue - if you have any! Because many people searching for a good solution
1.) Download SuperSU - current version 2.79 Stable (with Browser, not with Downloadmanager): https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip?retrieve_file=1 - it is the original one from Chainfire, not CCMT
2.) Download the Kernel - which allows you to Root: https://www.androidfilehost.com/?fid=385035244224383592
3.) Place both zips on the external SD
4.) Reboot to TWRP Recovery
5.) Make a comlete Nandroid Backup
6.) Navigate back to the main menu
7.) Use: Install - and navigate to the place of the Kernel-for-Root-Stock-MM.zip
8.) Swype to confirm flashing the Kernel-for-Root-Stock-MM.zip
9.) Directly after this flash navigate back to the main menu
10.) After go to the Advanced button and use the Terminal.
On the first screen tap on the ok button and after write following Force Systemless Command:
echo SYSTEMLESS=true>>/data/.supersu
and quit this with the ok tab
11.) Use the install button and navigate to SuperSU.zip
12.) Swype to confirm flashing SuperSU
13) Reboot your Phone
14.) If TWRP ask you for Root - "Your device does not appear to be rooted - Install SuperSU now?" - NO - use: DO NOT INSTALL Button!
Older Versions of TWRP ask you this - the newest TWRP 3.0.2 dont.
15.) P8 reboots now 2 times and rebooted finaly to system.
16 Open the SuperSU App (it will be on an empty site of your home) - you have now systemless Root with the latest stable SuperSU
Uninstall this kind of systemless Root:
If you like to Unroot your Phone from this systemless Root, do following steps:
1) If you have Xposed Framework installed - uninstall it with the uninstaller.zip (matching your phone) in TWRP - directly after you must Wipe Cache and Dalvik - next step: reboot your phone.
2) If you have BusyBox installed - uninstall it with BusyBox-Cleaner.zip in TWRP - Download: https://www.androidfilehost.com/?fid=24591000424941581
3) Reboot Phone open SuperSU and tap "complete Unroot"
4) If SuperSU ask you two times to restore the original Stock-Boot Image say: YES
5) Phone reboots automatically
6) Check it with Root Checker: succesfully unrooted
7) If the phone dont reboot automatically - reboot by yourself to TWRP
8) flash unsu.zip - Download: http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893 - reboot your Phone and Unroot is ready.
9) If the Download-Link of unsu.zip has changed, because it gets updates - you find it on this site: http://forum.xda-developers.com/showpost.php?p=63615067
10) Reboot your Phone - Root is uninstalled
After you have rooted your phone - it is recommended to flash Busybox in TWRP:
I always prefere BusyBox YDS by YashdSaraf for Huawei P8. This busybox recognizes which kind of Root and architecture you have and it will install to in the right directory. It uses also arm64 Binarys - just flash it after Rooting and first boot to system with TWRP.
You can find the Thread here: http://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
Use in Download Section the Universal zip or the ARM zip (it conains arm64).
Credits:
Many thanks to @Chainfire for his grandiose SuperSU
Many thanks to @AD2076 for the new TWRP-Recovery twrp-3.1.1-0-grace.img for Huawei p8 marshmallow.
And thanks a lot to @YashdSaraf for very good BusyBox
Last Update: 06.02.2018
Will this work on GRA-UL10?
Thanks a lot.
lordcookies said:
Will this work on GRA-UL10?
Thanks a lot.
Click to expand...
Click to collapse
Sorry for my late answer. I saw your message just right now. GRA-UL10 is Chinese Unicom Dual 4G model, with Kirin 935 chipset and 64GB ROM. Which firmware version do you have? The Root Method A should work without problem. Be sure you make before rooting a complete Nandroid Backup. If something goes wrong you can reboot to TWRP with hardware keys and restore system, data and boot. So nothing bad could happened.
The Methods B and C needs to flash the Custom Kernel, I don't know if it works with GRA-UL10. But with a Full TWRP Nandroid Backup you can try... Please let me know if it works for you
Info:The TWRP should work with GRA-UL10 without problems - or do you have another one working for marshmallow? If yes, please post. Thanks
Result without success
Hi, thanks for your post. I tried with the first option with SYSTEMLESS and STOCK Kernel. Everything worked as you described but after I tried to reboot the phone was dead. I had to reinstall the B370 update I had in /dload folder. I followed very carefully your instructions step by step.
First successful rooted boot, I updated SuperSu with the binary option and rebooted without problems. But one hour after I tried to reboot the phone manually and then the problem appeared.
My phone is working now but I don't know how to make this permanent. Do you have any idea?
Ps: attached screenshot of my current build
Thanks again!
juanzete said:
Hi, thanks for your post. I tried with the first option with SYSTEMLESS and STOCK Kernel. Everything worked as you described but after I tried to reboot the phone was dead. I had to reinstall the B370 update I had in /dload folder. I followed very carefully your instructions step by step.
First successful rooted boot, I updated SuperSu with the binary option and rebooted without problems. But one hour after I tried to reboot the phone manually and then the problem appeared.
My phone is working now but I don't know how to make this permanent. Do you have any idea?
Ps: attached screenshot of my current build
Thanks again!
Click to expand...
Click to collapse
Did you have a custom Rom before? I am wondering - normally the Model number shows Huawei GRA-L09 or GRA-UL00 and not GRACE. Grace is both http://consumer.huawei.com/tz/support/products/technicalspecs/grace-tz.htm?utm_source=Viber&utm_medium=Chat&utm_campaign=Private
So, which Model do you have? Please tell me.
You said you did it step by step with my instruction. I wrote several times to make a Backup of system, data and boot with TWRP. You had TWRP, otherwise you could not flash SuperSU. If the phone got a problem you could boot it to TWRP by holding vol+ and power key and restore the backup. No need to flash again the firmware. Didn't you make a TWRP Nandroid Backup?
The other thing I cannot understand is - normally it is absolutely necessary to flash back the Original Stock Recovery before doing any stock firmware update with dload. And it is also important to unroot. I am wondering if this was successful...
Which Rom (version) did you have before? Was your phone rooted before b370? Did you unroot before upgrade to this version? Did you make a full Wipe before upgrading or a factory reset? If you use b370 your model must be GRA-L09. Because the other models have not this version yet. (if my information is right)
I don't think the problem is the Root Method A.
If your Model is really a GRA-L09 I would recommend Root Method B or C with the custom Kernel. But if you use at the moment a Custom Rom instead of the stock firmware there would no need to root because having already root.
Something in the story is not conform but I need more information to get an idea what is the specific problem. Because I tested all three Versions without any problem...
No, I did not have a custom ROM. The GRACE model appeared as soon as I updated with an official B370 Europe. In fact I have my bootloader unlocked and I had to use this Model Name to get the unlock code from Huawei. Before doing the update I had GRA-L09.
Yes, I have a TWRP backup, I made it before rooting but I didn't use it because the only way to power on the device was either bootloader or recovery (Vol- & Power / Vol+ & Power)
When I tried recovery, Huawei's recovery appeared taking my update.app on /dload (didn't have any other option at that moment, the process started automatically). I didn't lose any data, the phone after the update started normally with all my settings exactly as it was before rooting, but this time SuperSU says the phone needs to be rooted.
For some reason TWRP is not installed anymore. If I try now, the Huawei Recovery starts. I currently have B370 same as before rooting. No full wipe before upgrading neither a factory reset.
I read that Huawei Stock recovery can rewrite your custom recovery, is that possible?
J.
Of course. After flashing the Recovery you must disconnect the USB cable from Phone and PC and boot manually with vol+ and power until you see the Huawei Logo. In that moment you must leave the power button but holding vol+ until the TWRP starts. This need a while. If you don't do this, Stock Recovery will be reflashed. Only the first boot to Twrp is important. After that TWRP will not be overwritten anymore. I am wondering about Model "Grace" I had b321a before and make the update with full firmware - after it shows me also GRA-L09 and not GRACE... Anyway. Sometimes things are strange. Okay. You must flash TWRP again and immediately after successful flashing manually boot to Twrp - but disconnect from PC!
Before all doing this be sure you have the Custom Kernel and SuperSU 2.76 on your SD. Flash first the Kernel and after SuperSU 2.76 - if you want systemless then with Force systemless Command before, if you want Root in System then without this command. And you will be happy and no more having problems with Root
The problem was, that you did not manually reboot to Twrp after flashing
@juanzete - Did you solve your problems now and Root is succesful? @lordcookies Did you try one of the root method for your GRA-UL00?
Tanks
Tanks a lot.It worked for me.(GRA-UL10):good:
---------- Post added at 09:33 AM ---------- Previous post was at 09:08 AM ----------
lordcookies said:
Will this work on GRA-UL10?
Thanks a lot.
Click to expand...
Click to collapse
Yes It Works.
SMhd3000 said:
Tanks a lot.It worked for me.(GRA-UL10):good:
---------- Post added at 09:33 AM ---------- Previous post was at 09:08 AM ----------
Yes It Works.
Click to expand...
Click to collapse
Which one of the three Root method did you use? I would like to know, thanks
GRA-L09, method 3 works but root isn't systemless. I am trying to install systemless xposed but it fails because of system mode root... Any ideas?
Before you ask:
I flashed the custom kernel properly
/data/.supersu is present and contains SYSTEMLESS=true
I said NO to TWRP root offer
AD2076 said:
GRA-L09, method 3 works but root isn't systemless. I am trying to install systemless xposed but it fails because of system mode root... Any ideas?
Before you ask:
I flashed the custom kernel properly
/data/.supersu is present and contains SYSTEMLESS=true
I said NO to TWRP root offer
Click to expand...
Click to collapse
Hi, I made a new Kernel specifically for SuperSU 2.78 - you can download it: https://www.androidfilehost.com/?w=files&flid=109256
Before you try method 3 with the new Kernel and the Original SuperSU 2.78: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip - you must Unroot your Phone and after install again. It should work.
I tested method 3 several times without any problems.
Tecalote said:
Hi, I made a new Kernel specifically for SuperSU 2.78 - you can download it: https://www.androidfilehost.com/?w=files&flid=109256
Before you try method 3 with the new Kernel and the Original SuperSU 2.78: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip - you must Unroot your Phone and after install again. It should work.
I tested method 3 several times without any problems.
Click to expand...
Click to collapse
I am gonna try it. Of course I unrooted before trying.
The big problem is I have to completely unroot at every reboot if I wanna play that throw a ball to the monster game
On another device I have systemless root + systemless xposed + suhide and I can play with no problems.
Does this kernel have adb enabled?
AD2076 said:
I am gonna try it. Of course I unrooted before trying.
The big problem is I have to completely unroot at every reboot if I wanna play that throw a ball to the monster game
On another device I have systemless root + systemless xposed + suhide and I can play with no problems.
Does this kernel have adb enabled?
Click to expand...
Click to collapse
If you have then succesful rooted and Xposed Framework installed you can try Module RootCloak
Tecalote said:
If you have then succesful rooted and Xposed Framework installed you can try Module RootCloak
Click to expand...
Click to collapse
RootCloack doesn't bypass SafetyNet check, suhide does.
I can root successfully but there are problems because the root isn't really systemless and SafetyNet detects it even with suhide.
Furthermore systemless xposed fails to install and complains about the supersu version < 2.76.
Of course I used 2.78
Btw your kernel works but required some reboots to work properly. At first boot SIM was not detected and the system was very very laggy.
I am available for more testing
Which Firmware to you use? I have tested it on b370, but with SuperSU 2.76- I will try it again in the evening with 2.78
I cannot understand yet, why it dont root systemless with method 3.
And RootCloack is available also with Support MM (new version) - do you mean, this dont hide root for your game? I write again, as soon I have time solving your issue.
Tecalote said:
Which Firmware to you use? I have tested it on b370, but with SuperSU 2.76- I will try it again in the evening with 2.78
I cannot understand yet, why it dont root systemless with method 3.
And RootCloack is available also with Support MM (new version) - do you mean, this dont hide root for your game? I write again, as soon I have time solving your issue.
Click to expand...
Click to collapse
I use B370 FF Edition from Blackball.
I just noticed I have an old twrp version: 2.8.7.0 by Jemmini. I am gonna upgrade and see if suhide works, it requires twrp > 3
B370 FF Edition is prerooted in Systemmode. I think, thats why the SuperSU Installer ignore perhaps the systemless command.
Dont know if there is a way to do it. May you ask Fromfuture in his Thread.
Or you install the Original Stock Version b370.
I used the completely unroot option in supersu before rooting systemless
THIS PROJECT IS NO LONGER SUPPORTED.
# F2FS Loopback Bug Workaround
## README.md
### Copyright (C) 2017-2018, VR25 @ xda-developers
#### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project; DO NOT share ready-to-flash-builds (zips) on-line!
---
#### DESCRIPTION
Some kernels from devices with F2FS-formatted data partition (i.e., Motorola) have a bug which prevents loopback devices (.img files) from being mounted read-write. This limits systemless modifications that can otherwise be achieved with Magisk.
This module works by moving magisk.img to the cache partition (EXT[2-4]-formatted) and linking it to its actual location (i.e., /data/adb/magisk.img). The other half of the process consists on automatically recreating magisk_merge.img shortly after boot and handling it the same way as magisk.img.
With this workaround, a patched kernel is dispensable.
Cache partition's size is essentially the only limiting factor -- and that's pretty much self-explanatory.
/cache/magisk_.img is automatically backed up to/data/adb on boot (only if modified) & restored on install. Thus, whenever cache is wiped, magisk_.img and its respective symlink can easily be restored by simply reinstalling the module.
---
#### PRE-REQUISITES
- Magisk v15+
- F2FS-formatted data partition
- EXT[2-4]-formatted cache partition
---
#### SETUP STEPS
Fist time
- Install from custom recovery as a regular flashable zip.
Upgrades
- Install from Magisk Manager or custom recovery.
- Reinstall after cache wipes to restore magisk.img backup.
---
#### NOTES/TIPS
Always install large modules from custom recovery only. In fact, I recommend installing every module from recovery if your device's cache partition has a very small size (i.e., only a few Megabytes).
To revert changes, uninstall the module, boot into custom recovery and delete </data/adb/magisk.img> & <magisk.img.bkp>. Lastly (while still in custom recovery), move </cache/magisk_.img> to </data/adb/magisk.img>.
Updates and reinstalls can be carried out from Magisk Manager as well.
---
#### ONLINE SUPPORT
- [Facebook Support Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/f2fs-loopback-bug-workaround/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875/)
---
#### RECENT CHANGES
**2018.10.9 (201810090)**
- Bug fixes
- Latest module template, with added sugar.
- Magisk 15-17.2 support
- Updated documentation
**2018.9.2 (201809020)**
- Improved compatibility
- Major optimizations
- Updated documentation
**2018.8.1 (201808010)**
- General optimizations
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk V16.6).
- Updated documentation
Works with stock roms as well ?
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Is this for Nougat or Marshmallow?
does this work on nougat update or only on MM?
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Anybody know how to fix notifications without breaking safety net?
VR25 said:
DISCLAIMER
Not taking responsibility for any thermonuclear war or cat harm. Do it at your any risk.
NEEDED
[Unlocked Bootloader] https://youshouldknowthisbynow.com
[Latest TWRP] https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629 credits @Alberto97
[Latest FSFS patched Kernel] https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732 credits @tomparr
[Latest Magisk zip] https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 credits @topjohnwu
[Latest Magisk Manager app] https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en credits @topjohnwu
PROCEDURE
0. reboot bootloader
1. fastboot boot twrp.img
2. adb sideload fsfs patched kernel
3. adb sideload magisk
4. reboot system
5. install magisk manager from play store
6. reboot bootloader [yes, again]
7. fastboot boot twrp.img [yes, again]
8. adb sideload magisk [yes, again]
9. reboot system [yes, ag... you get the point]
10. open magisk manager settings, enable "magisk hide"
11. reboot, done
Click to expand...
Click to collapse
Works like a charm.
I however did not temporarly boot into TWRP, I flashed it as such.
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
I'm on Android 7.0 Nougat.
Thanks!
Erwin
fortunz said:
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Click to expand...
Click to collapse
Hopefully your cat is ok now
jjdavis699 said:
Is this for Nougat or Marshmallow?
Click to expand...
Click to collapse
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
mhp1995 said:
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Click to expand...
Click to collapse
It should work on both Marshmallow and Nougat, as long as you pick the appropriate kernel for your system version (6 or 7). @mhp1995, I don't think the software channel matters. It should work across all (retus, retin , reteu, etc.).
xxBrun0xx said:
Anybody know how to fix notifications without breaking safety net?
Click to expand...
Click to collapse
No idea at this point, man. I've never had to fix mine. Perhaps only some people have it...?
@erwin, I chose not to touch the stock recovery to keep OTA installations straightforward. Easy for everyone.
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
mhp1995 said:
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
Click to expand...
Click to collapse
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
VR25 said:
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
Click to expand...
Click to collapse
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
mhp1995 said:
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
Click to expand...
Click to collapse
Oh, yes the availability... I forgot to mention that. Hopefully a proper Xposed version will be available for nougat very soon. When that happens, I'll update the thread.
About adding the tutorial to your thread... sure, go ahead.
I honestly declare I didn't read whole thread - is this method work for stock Nougat rom - I need root for Titanium Backup only for now , since facebook messenger goes crazy on my new phone MZP :-/ . Or maybe there is a way to restore old conversations ,not restored automatically in Facebook Messenger - anybody knows how to do it ? . On every phone I had I used root for two things mainly - Titanium Backup and to block adds - dns66 do block adds very well without root but , Titanium Backup has no alternative for me .
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
tag68 said:
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
Click to expand...
Click to collapse
[emoji4] but voting is only 3 works 2 not, so?
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
What is expected to be done for next OTA to work? Just restore Nandroid backup of boot partition and everything should be ready for patchlevel newer than January 2017, right? And afterwards f2fs fixed kernel and Magisk again for having root again of course.
(twrp not flashed, no logo modified, system should be untouched)
---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------
sebx_g1 said:
[emoji4] but voting is only 3 works 2 not, so?
Click to expand...
Click to collapse
Xposed does not work on Nougat by now. Magisk does. The 2 negative votes you counted referred to Xposed
Anyone have an adblock that works with systemless and passes safetynet? Do we need to check the "enable systemless for adblocks" in Magisk settings?
DNS66 do the same what do adblock, you can use it without root. But yes, there is special version of adblock systemless.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Worked fantastically, thanks a lot!
Hi all, i saw a lot of thread regarding root methods/procedures in this forum.
I wrote this post just to give an index, maybe someone can do a sticky post for this content, so here we go:
MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed from Lordbannakaffalatta
Very complete post, almost everything you need
[ROOT] Huawei P8 Lite ALE-L21, Android 6.0 Marshmallow from daviddosa
Sysless root, maybe?!need testers from Szabi01
For systemless root
[ALE-L21] All in one Megapack for P8 Lite [Download now available] from SuperProHacker
This is the only one i haven't used on my phone, systemless root with suhide and a lot of tools for P8 Lite
[2017.3.21] Magisk v11.6 - Root & Universal Systemless Interface [Android 5.0+] from topjohnwu
Used this just yesterday, after update ALE-L21C432B595 Full, the procedure from the post for a clear installation:
(Recommended) Restore your boot image back to stock (i had a full update just a few minutes before )
Install TWRP if not already present (step added by me!)
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode i did not this step, it's optional and only if you want supersu, i wanted to try without it
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
All credits goes to respective developers/authors, as i said this is just an index.
If i missed some thread just tell me so i can update.
I recently got a Pixel 2 XL and have been using Magisk right away. Because of the nuisance of updating I didn't update much in the past on my 6P with Magisk. On this device I'm determined to stay as up to date as possible when it comes to OTAs. I didn't have luck taking the January OTA using the recommended method on the Magisk site and I found many different methods. I decided this method was the most straightforward method for me. I'm sure others are already doing this, but I wanted to post my method of updating the device while keeping TWRP and Magisk.
-Make sure you have installed the platform-tools properly
-Download the desired FULL image from https://developers.google.com/android/images and extract the ZIP somewhere
-***IMPORTANT: REMOVE '-w' from the 'fastboot update' line in the flash-all.bat (this will stop it from wiping the device)
-Remove 'exit' from flash-all.bat
-Make sure you have already downloaded the latest Magisk ZIP (should be under '/sdcard/MagiskManager', ex. 'Magisk-v15.2.zip')
-Power off device
-Boot the device into fastboot (power + down)
-Run flash-all.bat
-Let phone boot into the OS
-Power off
-Boot the device into fastboot (power + down)
-Install TWRP (using instructions from https://twrp.me/Devices/Google/)
-fastboot boot *TWRP.img path*
-adb push *TWRP.zip path* /
-Install twrp.zip via TWRP interface-While still booted in TWRP, install Magisk ZIP via TWRP interface (ex. '/sdcard/MagiskManager/Magisk-v15.2.zip')
-Wipe cache/dalvik
-Reboot
You don't even need TWRP to take the OTA, Magisk has a built in way to take OTAs and still retain magisk.
Neverendingxsin said:
You don't even need TWRP to take the OTA, Magisk has a built in way to take OTAs and still retain magisk.
Click to expand...
Click to collapse
The reference to TWRP wasn't meant to imply that TWRP is required. I was just stating the easiest method that I used for a user who has a Pixel 2 device with Magisk AND TWRP. I was unable to take the OTA with Magisk after following the instructions on https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and that it is why I went this route.
Simple and straightforward, thanks mate! I'll give it a try.
Of course being an OTA it keeps all my stuff after I remove "-w" right?
Finally got around to trying this, it worked great!
hey mate i used these instructions to install the May OTA on my Pixel 1 and worked a treat. I would add at the start to remove any substratum overlays if used.
Also I uninstalled magisk before the process but not sure if you need to?
p.p.s. can a git please message this guy to re-test or remove his instructions here because there's multiple reports that they don't work!
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
gfunkzero said:
hey mate i used these instructions to install the May OTA on my Pixel 1 and worked a treat. I would add at the start to remove any substratum overlays if used.
Also I uninstalled magisk before the process but not sure if you need to?
p.p.s. can a git please message this guy to re-test or remove his instructions here because there's multiple reports that they don't work!
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Click to expand...
Click to collapse
Shouldn't have to remove anything because you are doing a full flash of the stock OS. It will just overwrite anything that is there.
Good evening All,
apologize in advance if this question has been already asked through the Forums, as I have been searched multiple times and spent some hours... ending almost in circle to the same articles.
HW: Samsung Galaxy Note 10+
AndroidOS: v9
Successfully rooted and installed Magisk v7.4.0 in 2019, via TWRP / Odin following this procedure:
How to Root Samsung Galaxy Note 10 and Note 10+
In this tutorial, we will show you how to unlock the bootloader and then root Samsung Galaxy Note 10/Note 10+ using Magisk. This guide supports Exynos variants of the Galaxy Note 10 and Note 10+ with…
www.thecustomdroid.com
A couple of days ago had the "brilliant" idea to update Magisk Manager to latest available version v.23.0: successful via the Manager app itself.
Now, when opening the Manager I get a "Unsupported Magisk Version" error.
Tried to remove and reinstall the Manager application multiple times without success.
Tried to install Magisk via the application itself, obviously selecting "Recovery Mode" as no Ramdisk for the device, via following Methods:
Direct Install (Recommended)
Select and Patch a File
Via Method #1. the installation is [apparently] completed without errors / warnings, and as soon as reboot is performed I go back to above "Unsupported Magisk Version" problem.
Via Method #2. I have successfully patched the "recovery.img" file from device firmware, used in original installation, and saved on local MicroSD. I have not yet tried to install it via TWRP as I am concerned to brick the device, as no other spare device exists.
Current situation:
- - - -
Magisk
Installed N/A
Ramdisk No
A/B No
SAR Yes
App
Latest App 23.0 (23000)(21)
Installed App 23.0 (23000)
- - - -
The vast majority of the articles found on XDA and via web search bring to fresh installation guidelines / procedures:
https://topjohnwu.github.io/Magisk/install.html [the MASTER one from the developer]
Install Magisk in Recovery and Root Android [No Ramdisk]
In this guide, we will show you how to install Magisk in the recovery partition and then root your Android device that doesn't have Ramdisk.
www.droidwin.com
Any input would be much appreciated.
Regards.
One more detail.
"root" privileges are still there, as I can boot into the rooted system with Magisk.
TitaniumBackup is working correctly - as example: I have previously tried to restore the previous Magisk Manager v7.4.0 version, but this did not achieve anything - I believe because of multiple "dependencies" and possible updated files / libraries across the filesystem.
Enriching this post, by proposing one of the following options:
#1.flash via TWRP the newest Magisk (yes, no "Manager" exists anymore) .apk
#2. flash via TWRP the patched "recovery.img"
open to your valuable suggestions.
Hello, I had a similar issue with my Note 10. It fixed itself by continuing to restart my phone and trying to turn on Magisk by holding down the Volume Up and power buttons at the same time.
The fourth time I tried Magisk finally worked.