Phone: Huawei P20 Lite
ROM: Omni
Magisk: 20.3
Downloaded the Magisk.zip file through Magisk manager.
Flashing the Magisk zip using TWRP is success.
But rebooting to system showing Magisk isn't installed.
So I was to try flash it again. But booting TWRP is failed.
It ended up booting to system. At this time Magisk manager showing it as installed.
To be concluded:
1) Rebooting to system will delete Magisk root.
2) Rebooting to recovery (TWRP) will fail and boot to system. In that case Magisk manager saying root installed
Any solution to make root access stable and keep TWRP in recovery partition?
4n3y3 said:
Phone: Huawei P20 Lite
ROM: Omni
Magisk: 20.3
Downloaded the Magisk.zip file through Magisk manager.
Flashing the Magisk zip using TWRP is success.
But rebooting to system showing Magisk isn't installed.
So I was to try flash it again. But booting TWRP is failed.
It ended up booting to system. At this time Magisk manager showing it as installed.
To be concluded:
1) Rebooting to system will delete Magisk root.
2) Rebooting to recovery (TWRP) will fail and boot to system. In that case Magisk manager saying root installed
Any solution to make root access stable and keep TWRP in recovery partition?
Click to expand...
Click to collapse
you can patch magisk to your firmware and install (flash) it with odin. but from my experience, the jhonwu method is really work (magisk in system as root) but I am unable to install twrp alongside that system. I mean yes indeed I can flash twrp into the device but then I lose root access. (many case I got random restart all over again).
now I am kinda confused because I need root and also that twrp is really usefull tool for idiot like me.
FYI; I already try install twrp pre-patched magisk from geiti, but its very unstable. random reboot, and sometimes I am losing the magisk it self (magisk manager suddenly show that magisk isnt intall). thats why I am kinda prefer to root with jhon wu method,
can you guys help me how to flash twrp without ruin magisk that already installed on patched stock firmware?
Related
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 installed magisk through flashing zip in twrp (tried v16, v16.6 and v16.7 beta) on my moto x4 (stock boot.img, Android 8.0), installation works but when I reboot to system I get stuck in a bootloop. I installed "mm" module and it shows the installed module, so I guess magisk is installed correctly. I tried looking for a magisk log in /cache but it is empty, and since it does not even get to the "normal" stage of a system boot I also got no adb logs. I also tried patching the stock boot.img with magisk manager and flashing this, but that also results in a bootloop. Really not sure what I'm doing wrong, I checked tutorials/videos (also specifically for my device) and it's rather straight forward, just flash the zip and done. Any help would be appreciated.
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!
Dear XDA,
Model: Xiaomi Redmi 4X(Santoni)
Used TWRP:
Installed latest Lineage OS 16.0 of November 20, 2019 with formatting internals and wiping system, vendor, dalvik and cache.
Installed lastest Magisk v20.1 from GitHub page
Booted ROM and installed "MagiskManager-v7.4.0.apk" from above link
As the result:
MagiskManager shows everything green
No root prompt in any application and Root Checker shows that root is not installed.
"Settings -> System -> 'Developer options' -> 'Root access'" have only two options: Disabled and "ADB only"
Already have tried:
Disabling power optimization entry for MagiskManager
Reinstall Magisk using MagiskManager
What might be the reason of no prompt issue?
Why not SuperSU: is it worth to tell why? For example, basically Netflix won't work etc.
Thank you very much for any working suggestion.
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
I Have Nexus 5x and Lineage OS 15.1.
For me it was Lineage OS issue. Instead 20191118 I flashed 20191105. I had some other weird bugs too.
Ænimal said:
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
Click to expand...
Click to collapse
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
vv77vv said:
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
Click to expand...
Click to collapse
I thought I expressed myself pretty clearly. Well, a clean install of your system is always a good idea (given you backed up all your personal data) .You can also just extract the boot.img from your LOS image and flash that in twrp prior to flashing magisk. But what I did when the root prompt didn't pop up was simply flashing the magisk zip again in twrp, (maybe wiping caches as well) and after rebooting magisk su was working as intended.. Good luck
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