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
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).
Hey guys, can anyone tell me which version of supersu you used to install root on the latest 4.0.3 rom?
I tried flashing the latest UPDATE-SuperSU-v2.79-20161211114519 and the older SuperSU-v2.79-201612051815, but both seem to get stuck on boot. I tried waiting for an hour just to be sure. I also tried flashing no-dmverity after flashng supersu, but that didn't help either.
Will appreciate some help.
Hey,
I used SuperSU v2.79-20161211114519
https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip
Worked without problems for me.
Are you clean flashing?
EDIT: also, are you using the latest 3.0.4-1 TWRP?
knijntjes said:
Hey,
I used SuperSU v2.79-20161211114519
Worked without problems for me.
Are you clean flashing?
EDIT: also, are you using the latest 3.0.4-1 TWRP?
Click to expand...
Click to collapse
Yeah, I clean flashed it. Used twrp 3.0.4-1 , 3.0.4-0 and 3.0.3-1 - but none worked.
Also tried going stock recovery, flashing ROM, flashing twrp and then supersu. That didn't work too.
Azureum said:
Yeah, I clean flashed it. Used twrp 3.0.4-1 , 3.0.4-0 and 3.0.3-1 - but none worked.
Also tried going stock recovery, flashing ROM, flashing twrp and then supersu. That didn't work too.
Click to expand...
Click to collapse
You could try to flash only no-dmverity without superuser to see if you can get twrp working with 4.0.3.
If that works you could try again, or maybe use PHH Superuser?
knijntjes said:
You could try to flash only no-dmverity without superuser to see if you can get twrp working with 4.0.3.
If that works you could try again, or maybe use PHH Superuser?
Click to expand...
Click to collapse
Yeah I did that too. The ROM works without supersu. But after that when I flashed supersu, it got stuck on boot.
Will try PHH superuser at a later time. Also there's no way to remove dm-verity warning message on 4.0.3, right?
I'm having the same issue - installing 4.0.3 and then flashing SuperSU 2.79 results in a boot sequence that never ends (not a loop, just sits there with spinning icons forever).
Haven't tried it without SuperSU so for now sticking to 4.0.2
Also have the same question about removing the dm-verity message on boot.
gigo08 said:
I'm having the same issue - installing 4.0.3 and then flashing SuperSU 2.79 results in a boot sequence that never ends (not a loop, just sits there with spinning icons forever).
Haven't tried it without SuperSU so for now sticking to 4.0.2
Also have the same question about removing the dm-verity message on boot.
Click to expand...
Click to collapse
No problems here with SuperSU 2.79 sr3
For removing dm verity error you can search for a thread here on xda
It involves flashing 4.0.2 firmware image then executing fast boot commands to remove that error and then flash back 4.0.3 firmware
kunal1540 said:
No problems here with SuperSU 2.79 sr3
For removing dm verity error you can search for a thread here on xda
It involves flashing 4.0.2 firmware image then executing fast boot commands to remove that error and then flash back 4.0.3 firmware
Click to expand...
Click to collapse
Interesting, I hadn't tried any of the beta SuperSu releases. What version of TWRP did you use? I'll give this a try later.
Interesting, I hadn't tried any of the beta SuperSu releases. What version of TWRP did you use? I'll give this a try later.
Click to expand...
Click to collapse
I used a Twrp 3.0.4-1 image. The official Twrp 3.0.3-2 may have a problem with Oxygen 4.0. But instead of SuperSU, after unlocking and installing Twrp, I flashed Magisk 11.1.zip from Twrp. Magisk 11.1 contains its own MagiskSU. After installing Magisk, install "Magisk Manager" from the Playstore. In Magisk Manager open the menu (tap the 3 horizontal lines at top left) and select settings. Turn on Enable BusyBox, Magisk Hide, and Systemless hosts. Press the back arrow at the top to get the menu back and select status. Now check SafetyNet and it should pass. If you passed SafetyNet, your can safely set up your security (PIN and fingerprint). Try starting an app that needs root. In the Magisk Manager menu select SuperUser and it will list all the apps granted root permission. Each entry there has an on/off switch. If you tap an entry more options will be shown.
Instead of unlocking your phone in order to flash twrp, try booting twrp: "fastboot boot twrp-3.0.4-1-oneplus3.img". Then use this temporary twrp to install Magisk. If it works, you can root your phone without unlocking it and wiping your data. (I would try it, but I'm already unlocked).
How I rooted details: I already had abb and fastboot installed on my pc. After the OEM upgrade to Oxygen 4.0.3, change lock screen security to swipe (no security). Connect phone to pc using the original charging cable. Enable Developer options (by tapping "about phone" in Settings 7 times). In Developer options turn on OEM unlocking, Advanced reboot, and USB Debugging. Hold the power button until it offers to Reboot or Power off. Select Reboot, then select Bootloader, then touch to reboot. Open cmd window in adb folder (hold shift and right click on a blank spot in folder and select Open command window here ) In cmd prompt type fastboot devices and press enter. If it finds your device type fastboot oem unlock and press enter. Use volume keys to select >> YES and briefly press power key. Wait for it to finish wiping the data partition. Now you are "unlocked" (flashing enabled). Type fastboot flash recovery <twrp image> and press enter where <twrp image> is your TWRP 3.0.4-1.img file name (the official twrp, 3.0.3-2 has problems with Oxygen 4) Type in the name of this file, or drag and drop the file to the cmd window, or copy it's name (with just one .zip on the end) and paste it into cmd window by clicking on the black icon in the upper left corner, scrolling to Edit, then click Paste). After it's finished flashing, use the volume keys to select recovery and briefly press power button to boot into TWRP. In TWRP swipe right to enable writing to the system partition (however we will NOT change a single bit in system so we can pass SafetyNet). Install your Magisk v 11.1 zip file (it's a system-less app). Reboot to system. Proceed with downloading Magisk Manager from the PlayStore.
Hi, is it possible to update to Oxygen 4.0.3 after rooted and having magisk 11.1? I am currently on 4.0.2
HolyJeepers said:
I used a Twrp 3.0.4-1 image. The official Twrp 3.0.3-2 may have a problem with Oxygen 4.0. But instead of SuperSU, after unlocking and installing Twrp, I flashed Magisk 11.1.zip from Twrp. Magisk 11.1 contains its own MagiskSU. After installing Magisk, install "Magisk Manager" from the Playstore. In Magisk Manager open the menu (tap the 3 horizontal lines at top left) and select settings. Turn on Enable BusyBox, Magisk Hide, and Systemless hosts. Press the back arrow at the top to get the menu back and select status. Now check SafetyNet and it should pass. If you passed SafetyNet, your can safely set up your security (PIN and fingerprint). Try starting an app that needs root. In the Magisk Manager menu select SuperUser and it will list all the apps granted root permission. Each entry there has an on/off switch. If you tap an entry more options will be shown.
Instead of unlocking your phone in order to flash twrp, try booting twrp: "fastboot boot twrp-3.0.4-1-oneplus3.img". Then use this temporary twrp to install Magisk. If it works, you can root your phone without unlocking it and wiping your data. (I would try it, but I'm already unlocked).
How I rooted details: I already had abb and fastboot installed on my pc. After the OEM upgrade to Oxygen 4.0.3, change lock screen security to swipe (no security). Connect phone to pc using the original charging cable. Enable Developer options (by tapping "about phone" in Settings 7 times). In Developer options turn on OEM unlocking, Advanced reboot, and USB Debugging. Hold the power button until it offers to Reboot or Power off. Select Reboot, then select Bootloader, then touch to reboot. Open cmd window in adb folder (hold shift and right click on a blank spot in folder and select Open command window here ) In cmd prompt type fastboot devices and press enter. If it finds your device type fastboot oem unlock and press enter. Use volume keys to select >> YES and briefly press power key. Wait for it to finish wiping the data partition. Now you are "unlocked" (flashing enabled). Type fastboot flash recovery <twrp image> and press enter where <twrp image> is your TWRP 3.0.4-1.img file name (the official twrp, 3.0.3-2 has problems with Oxygen 4) Type in the name of this file, or drag and drop the file to the cmd window, or copy it's name (with just one .zip on the end) and paste it into cmd window by clicking on the black icon in the upper left corner, scrolling to Edit, then click Paste). After it's finished flashing, use the volume keys to select recovery and briefly press power button to boot into TWRP. In TWRP swipe right to enable writing to the system partition (however we will NOT change a single bit in system so we can pass SafetyNet). Install your Magisk v 11.1 zip file (it's a system-less app). Reboot to system. Proceed with downloading Magisk Manager from the PlayStore.
Click to expand...
Click to collapse
Is twrp. 3.0.4-1 and magisk v. 11.1 zip.. Adb folder.
Thats all..
Can anyone make a video of it please thanks
After I've applied the OTA updated for Android Pie(V10.0.2.0.PDIMIFJ), using the classic restore image, apply OTA, patch image, reboot and profit. My phone started bootlooping, my first move was to restore boot.img, done, working again. Then I patched the original boot.img and flashed it using fastboot, the bootloop returned. Tried to clear ddr after flashing the patched image, reinstalled magisk manager, repatched boot.img, no success at all. Anyone having trouble installing magisk on PIE(V10.0.2.0.PDIMIFJ)?
Regards,
xdxita said:
After I've applied the OTA updated for Android Pie(V10.0.2.0.PDIMIFJ), using the classic restore image, apply OTA, patch image, reboot and profit. My phone started bootlooping, my first move was to restore boot.img, done, working again. Then I patched the original boot.img and flashed it using fastboot, the bootloop returned. Tried to clear ddr after flashing the patched image, reinstalled magisk manager, repatched boot.img, no success at all. Anyone having trouble installing magisk on PIE(V10.0.2.0.PDIMIFJ)?
Regards,
Click to expand...
Click to collapse
Search patched_boot.img for 10.0.2.0.PDIMIFJ and magisk manager.apk
Code:
fastboot boot patched_boot.img
Install magisk manager if is not already installed
Open Magisk manager and use Install option and select recommended instalation option
Reboot and you are rooted
fast_retina said:
Search patched_boot.img for 10.0.2.0.PDIMIFJ and magisk manager.apk
Code:
fastboot boot patched_boot.img
Install magisk manager if is not already installed
Open Magisk manager and use Install option and select recommended instalation option
Reboot and you are rooted
Click to expand...
Click to collapse
Hey! Actually the problem is related to some module i've installed, to remove this module I have to boot TWRP and remove magisk files, problem is that the \data is encrypted and current version of TWRP(or PBRC) is unable to decrypt . My only option so far is to format data. But i'm still waiting for a updated version of some recovery. Or any other ideas besides format.
Cheers!
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Thanks, works great.
Daniehabazin said:
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Click to expand...
Click to collapse
Can you provide download links and instructions on how you have rooted EMUI 9.1 mate 20 pro.
I tried to root, but unable to mount few partitions. I have formatted "/data" using TWRP but still unable to flash magisk. After mutiple retries able to flash magisk with some errors mentioning about error in mount. Then my mobile keeps on rebooting and going to erecovery. Am on EMUI 9.1.0.300
adaway is working fine for me.
side_flip15 said:
adaway is working fine for me.
Click to expand...
Click to collapse
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
sharath91221 said:
Can you provide download links and instructions on how you have rooted EMUI 9.1 mate 20 pro.
I tried to root, but unable to mount few partitions. I have formatted "/data" using TWRP but still unable to flash magisk. After mutiple retries able to flash magisk with some errors mentioning about error in mount. Then my mobile keeps on rebooting and going to erecovery. Am on EMUI 9.1.0.300
Click to expand...
Click to collapse
there is no difference rooting 9.0 or 9.1, you do it the same way.
well, with the exeption that directly after factory reset you have to flash the recovery_ramdisk, if you let the phone boot up without the modified recovery then android messeges stops working.
so the step is simple, install 9.1, if your phone is messed up use the hstool or erecovery, hstool was faster for me.
get yourself a patched recovery_ramdisk from 9.1 (i did this myself by extracting the ramdisk and patching in magisk on my phone when i was still on 9.0)
before first boot, enter fastboot and flash the recovery_ramdisk.
boot with volume up, and then profit.
for more information check: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Daniehabazin said:
there is no difference rooting 9.0 or 9.1, you do it the same way.
well, with the exeption that directly after factory reset you have to flash the recovery_ramdisk, if you let the phone boot up without the modified recovery then android messeges stops working.
so the step is simple, install 9.1, if your phone is messed up use the hstool or erecovery, hstool was faster for me.
get yourself a patched recovery_ramdisk from 9.1 (i did this myself by extracting the ramdisk and patching in magisk on my phone when i was still on 9.0)
before first boot, enter fastboot and flash the recovery_ramdisk.
boot with volume up, and then profit.
for more information check: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
You used patched_recovery_ramdisk.img from 9.0 on 9.1 or you have extracted recovery_ramdisk from 9.1 and then patched it using magisk?
If you have extracted recovery_ramdisk.img from 9.1, can you provide me the link?
sharath91221 said:
You used patched_recovery_ramdisk.img from 9.0 on 9.1 or you have extracted recovery_ramdisk from 9.1 and then patched it using magisk?
If you have extracted recovery_ramdisk.img from 9.1, can you provide me the link?
Click to expand...
Click to collapse
i extracted the ramdisk from 9.1.0.310 and patched it in magisk on my phone. i'm unable to share the file right now because i'm on a trip right now but i'll be back on monday. but it's easy to patch it yourself, just extract it with huaweiupdateextractor and transfer it to your phone.
Daniehabazin said:
i extracted the ramdisk from 9.1.0.310 and patched it in magisk on my phone. i'm unable to share the file right now because i'm on a trip right now but i'll be back on monday. but it's easy to patch it yourself, just extract it with huaweiupdateextractor and transfer it to your phone.
Click to expand...
Click to collapse
Great. Thank you Daniehabazin :good:. I will download 9.1.0.310 using firmware finder app and extract UPDATE.APP using hauweiupdatextractor and use magisk to patch ramdisk.
sharath91221 said:
Great. Thank you Daniehabazin :good:. I will download 9.1.0.310 using firmware finder app and extract UPDATE.APP using hauweiupdatextractor and use magisk to patch ramdisk.
Click to expand...
Click to collapse
sounds good, hit me up for the patched ramdisk if you can't get it to work and i'll upload it on monday.
have a lya-l29c432 but the firmware i downloaded was for lya-lgrp-ovs, i guess it covers several hardware versions
Daniehabazin said:
sounds good, hit me up for the patched ramdisk if you can't get it to work and i'll upload it on monday.
have a lya-l29c432 but the firmware i downloaded was for lya-lgrp-ovs, i guess it covers several hardware versions
Click to expand...
Click to collapse
After factory reset, I have flashed patched ramdisk.img from 9.1.0.310 and while rebooting press and hold vol+ button, it is going to "press power key to continue, press volume up key..." thing. If i reboot and press vol- key again it was going to "press power key to continue...."thing. Magisk app still shows it was not installed.
Off topic for rooting... There is already a thread for that with patched recovery img 9.1 and procedure for rooting. 9.1...(search my posts) To return to subject of this topic, what is missing and why I don't use energized it's because it don't have blocklist GoodbyeAds (Google ads)
Also you can use private dns in network setting and put dns.adguard.com in it, but in my case that break mms so...
---------- Post added at 10:58 PM ---------- Previous post was at 10:56 PM ----------
Daniehabazin said:
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
Click to expand...
Click to collapse
Wrong, it's only "/system" and "/" r/o. Subfolders are r/w (ie /etc /cache...)
Daniehabazin said:
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
Click to expand...
Click to collapse
Take a look at my screenshots. I got something like storage error at first. Adaway worked after I debloat and systemize app using magisk module. Not sure if it's related but works for me three times already. Those two modules actually alters files on /system without any issue. Worth trying...
sharath91221 said:
After factory reset, I have flashed patched ramdisk.img from 9.1.0.310 and while rebooting press and hold vol+ button, it is going to "press power key to continue, press volume up key..." thing. If i reboot and press vol- key again it was going to "press power key to continue...."thing. Magisk app still shows it was not installed.
Click to expand...
Click to collapse
Trick is not to send command on fastboot to reboot. After flashing recovery_ramdisk successfully remove the usb cable then press and hold power + volume up buttons. Release them when you see the yellow text warning saying "your device is booting now..."
side_flip15 said:
Trick is not to send command on fastboot to reboot. After flashing recovery_ramdisk successfully remove the usb cable then press and hold power + volume up buttons. Release them when you see the yellow text warning saying "your device is booting now..."
Click to expand...
Click to collapse
I found an another way. After flashing patched ramdisk and after reboot if it shows "press power key to continue.." thing. Go to erecovery and then go to factory wipe. It does not actually wipe the phone, it simply reboots and turn on with magisk installed.
Now am unable to install exposed or core. If i install them, mobile is stuck at boot
side_flip15 said:
Take a look at my screenshots. I got something like storage error at first. Adaway worked after I debloat and systemize app using magisk module. Not sure if it's related but works for me three times already. Those two modules actually alters files on /system without any issue. Worth trying...
Click to expand...
Click to collapse
oh, ok.
because i also got the storage error and on the thread for p30 pro rooting i saw that adaway doesn't work, checked the p30 forum because they got their phone with 9.1.
i'll try adaway again, but i also kinda like the feeling of running a terminal on my mate 20 pro
Adaway is working just fine here in LYA 9.1.
But Energizer should be also fine.
oslo83 said:
Adaway is working just fine here in LYA 9.1.
But Energizer should be also fine.
Click to expand...
Click to collapse
Yes if systemless host is enabled. This is the trick. You can use all ad blocker apps.
Daniehabazin said:
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Click to expand...
Click to collapse
Great work, just did it and it works. Have been busting my head for a week now without Adaway. Thanks man!
adaway just works fine on 9.1