Huawei MediaPad M3 Lite 8 using TWRP 3.2.1-0
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting" at the Boot image patcher stage, which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread, can't post links yet) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help? I have posted in the relevant threads on the Mediapad M3 forum but it's a relatively small community.
Has somebody solved this very common problem¿
Related
Error: There is no Su binary installed, and SuperSu cannot install it. This is a problem!
Phone my nexus 6p on android 7. I installed through twrp UPDATE-SuperSU-v2.76-20160630161323.zip I have everything working. We have a smartphone all put this file.
But yesterday I flew root and gives this error. I reflash file, but the error is not corrected. I even pierced archive 2.77 beta.
How to decide?
Another version of TWRP, which supports android 7 for my phone no.
After resetting data - earned.
I have faced the same problem
I believe, in Nougat, updating the binaries, via the app, that it's failing for a bunch of individuals because (from what I've seen) SuperSU is having trouble with temporarily changing the Selinux Mode to permissive that allows the Binaries to be installed.
Have you tried to flash the SuperSU? Flashing it also updates the Binary files too.
Sent from my D2VZW on the Bridge of the U.S.S. Enterprise.
If you have magisk installed, remove it via uninstall.zip before flashing su. That worked for me
http://forum.xda-developers.com/gen...53-5-2-fhd-2gb-ram-16gb-t3341297/post70312604
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Code:
Installation Instructions
(NOTE: I don't feel comfortable to redistribute SuperSU unless I have explicit permission, so for now, if you want to use SuperSU with Magisk, you are required to have systemless SuperSU installed before flashing Magisk. Magisk will detect SuperSU installation and automatically convert systemless SuperSU into a Magisk Module, using the files that are already installed to your boot image. System installed SuperSU is obviously not supported, since it is not systemless. Actually, it is a trivial task to add official Magisk support to a SuperSU zip package, however the decision is not in my hands.)
If you're rooted with Official Systemless SuperSU, or using Magisk v3+ with Magisk version of phh's superuser
Install the latest Magisk Manager
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, rooted with the depreciated Magisk Version of SuperSU, using Magisk version older than v3, or you got issues when flashing in Magisk Manager (some devices requires Magisk to be flashed in recovery to find boot image location)
(If you have Magisk installed) Flash Magisk Uninstaller to get a clean start
Download the latest Magisk zip file
Download the latest Magisk Version phh superuser from this thread:
[Magisk] [2016.10.4] phh's SuperUser
Flash both zips in custom recovery
Install the latest Magisk Manager for a complete Magisk experience
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
NotExist said:
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
Click to expand...
Click to collapse
Am using an honor 7 PLK-L01 with MM build B370.
Also tried the first method you described with SuperSU 2.62, difference being that magisk manager could not install v7 zip so flashed it manually. It said something about
Insufficient storage for boot image
and kind of aborted.
Since then flashing SuperSU says seplocy failed and aborts.
Tried flashing a new boot and rooting, still the same.
Flashed boot and Cust, the same error both with magisk and SuperSU.
Cleared dalvik and cache, still the same.
Tried the magisk uninstaller, no success...
Would appreciate a solution.
Sent from my PLK-L01 using XDA Labs
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
ibrokemypie said:
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
Click to expand...
Click to collapse
Had to flash system, boot and Cust to root again using SuperSU.
Otherwise it was failing and flashing only boot did not cut the deal.
Sent from my PLK-L01 using XDA Labs
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
HyperCriSiS said:
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
Click to expand...
Click to collapse
Magisk ver 6 works well but have to have that zip and it's corresponding apk I guess 1.2 that is.
Used it a couple of days ways back just to make sure it works.
An update that it works after Magisk v8, although there's no information about it.
(Flash SuperSu v2.65 -> Update to SuperSU v2.78 with Google Play -> update su binary to v2.78 with SuperSU -> install Magisk Manager v2.1 -> Install Magisk v8 with Manager -> done!)
I have a problem when I go to open SuperSU tells me: SU Binary occupied, so it does not allow me to properly use the magisk manager.
I followed the guide for huawei, I did everything step by step, but nothing has ever given me this message.
How do I fix it?
Same here
I had this 2 but managed to fix it wat version of supersu are u using wat version of magisk r u using also
ditto.
SuperSU Free v2.82 & Magisk v13.3
eonix said:
ditto.
SuperSU Free v2.82 & Magisk v13.3
Click to expand...
Click to collapse
Since Magisk v13, there's no longer any compatibility for SuperSU. If you've flashed Magisk you're rooted with MagiskSU and that's why SuperSU is complaining about the binary being occupied.
You're unfortunately going to have to choose one or the other.
Am using asus zenfone 2 laser ze500kl..I rooted my device and when i booted my phone super su app is installed..but when i open the app it says su binary occupied..root checker app says that the root access is not properly installed...pls help
Vchuz said:
Am using asus zenfone 2 laser ze500kl..I rooted my device and when i booted my phone super su app is installed..but when i open the app it says su binary occupied..root checker app says that the root access is not properly installed...pls help
Click to expand...
Click to collapse
Hi! Had your same problem today with my Asus Zenfone 2 Laser ze500kl. Solved by following the exact steps of this guide, but instead of downloading and installing the suggested SuperSu zip file I found this older SuperSu version, downloaded the zip file, placed it in the internal storage and followed the exact steps of the guide. (For good measure, I did all the steps in the guide again).
Once you reboot your phone, you will be able to update the SuperSu app form the PlayStore to get the latest version. Should work just fine.
Good evening lads. I've been having problems installing Magisk.
I've successfully rooted my device (a Samsung J5 2016) and installed Magisk Manager. From there, I selected "Install" and after the confirmation that I want to install Magisk v20.4(204000) I choose "Direct Install" , which is also the recommended option but get an installation error.
Here's my log:
Code:
- Target image: /dev/block/mmcblk0p16
- Device platform: armeabi-v7a
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
! Installation failed
I'm very noob at this and barely have any idea with what I'm doing, so I'm asking you, what can I do? I checked other threads but their logs was very different.
I've never had any other problem with other root apps (Lucky Patcher, Titanium Backup, Root checker etc.) and all I want to do is hide my root so I can use the Nintendo Switch app, lol.
Thanks in advance for your help.
The usual answer is, into Recovery and flash Magisk Uninstaller, then install the Magisk file in Recovery.
I can't give any guarantees, but that always used to be the way to go, if Magisk did not install with Direct Install option.
Like I say, no guarantees.
Should have said, make a Recovery Backup before attempting.
Second thoughts, another poster has just reported a problem installing 20.4 in TWRP, so maybe it's not such a good idea after all.
I don't advise.
Sorry for wrong advice.
Sent from my SM-G965F using Tapatalk
if anyone is having trouble while installing magisk I have come up with solutions.
if you have installed magisk but it never detects as it is installed the following would be solutions i have found for my self
install magisk that is older than the one you are going to install in recovery with sideload for eg. to install magisk 25.00 from the recovery you need to install magisk 24.1 apk before that without shutting down your phone.
the second step you need to do is you have to side-load the latest version after you have installed the older version from the recovery
that is it simple as it is
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.