[HELP] Pixel3a Bootloop when Magisk Installed - Magisk

Hey Guys,
I was experimenting with some SELinux context labeling rules a couple of days ago in Android10 related to JamesDSP and my own Audio Mod Project. I had tried to inject a new rule via 'magiskpolicy' (it was a name_transition rule which I was hoping would re-label the library files in /vendor/lib/soundfx from a system_file context to vendor_file) in a few ways; first via command line using the --live argument which resulted in a Segmentation Fault, then again without the --live argument which resulted in no error and then finally I added the rule to a Magisk Module and installed that. Neither of the command line attempts had any result on the running system and after installing the Magisk Module and rebooting I started hitting bootloops.
I managed to get out of the bootloop by flashing the entire Factory Stock Image, but now everytime I try to re-install Magisk (by putting the Stock Boot Image onto the phone, installing MagiskManager, selecting the Boot Image to patch and then using fastboot to flash the patched boot image) the resulting Magisk Boot Image causes a bootloop. I've found that, for some reason, this particular pre-patched boot image with modded kernel works : https://forum.xda-developers.com/pixel-3a/development/kernel-stock-kernel-plus-f2fs-t3945936 (specifically the stock-modified-android10-1203-magisk.img one; the latest one also causes my phone to bootloop).
I'm a bit stumped on this... wondering if anyone has any ideas? Maybe I somehow corrupted the device's SELinux Policy, but I expect that to be replaced when I flashed the Factory Stock Image...
Update : This is the SELinux Policy Rule that I tried to add (same rule for all 3 attempts) : name_transition hal_audio_default system_file file vendor_file libTestEffect

Have you cleared /data? If you haven't your Magisk module (in /data/adb/modules) will still be active as soon as you install Magisk again, hence the bootloop.
Take a look here for some tips on how to remove it:
https://didgeridoohan.com/magisk/Magisk#hn_Disablinguninstalling_modules_manually

Jman420 said:
I'm a bit stumped on this... wondering if anyone has any ideas? Maybe I somehow corrupted the device's SELinux Policy, but I expect that to be replaced when I flashed the Factory Stock Image...
Click to expand...
Click to collapse
Like was mentioned above, you need to remove your module. You could try this:.
Root your phone again. When you bootloops, fastboot boot one of the images here. One will boot core-only, the other remove magisk and all modules so that you should be able to root again without bootlooping.
https://forum.xda-developers.com/pi...disabler-booting-magisk-t3976621#post81547783

Tulsadiver said:
Like was mentioned above, you need to remove your module. You could try this:.
Root your phone again. When you bootloops, fastboot boot one of the images here. One will boot core-only, the other remove magisk and all modules so that you should be able to root again without bootlooping.
https://forum.xda-developers.com/pi...disabler-booting-magisk-t3976621#post81547783
Click to expand...
Click to collapse
The module is most definitely gone. While I was running Magisk 20.1 I ensured that the /data/adb/modules folder was empty and then tried the steps you suggested above. The boot images provided in that thread also cause bootloops on my phone, both of them. The only guess I can come up with is that the 'magiskpolicy' commands I ran somehow changed something that doesn't get overwritten...

Jman420 said:
The module is most definitely gone. While I was running Magisk 20.1 I ensured that the /data/adb/modules folder was empty and then tried the steps you suggested above. The boot images provided in that thread also cause bootloops on my phone, both of them. The only guess I can come up with is that the 'magiskpolicy' commands I ran somehow changed something that doesn't get overwritten...
Click to expand...
Click to collapse
The method I showed you was for fixing a problem where there is a module installed that you could not remove due to a bootloop. That is the only problem it was meant to fix. If your module was already gone then it was pointless to try it.

Tulsadiver said:
The method I showed you was for fixing a problem where there is a module installed that you could not remove due to a bootloop. That is the only problem it was meant to fix. If your module was already gone then it was pointless to try it.
Click to expand...
Click to collapse
Agreed... but I'm trying every port in this storm. It's such a strange issue... At this point I've got the phone running the latest Factory Image, but have flashed the boot image I mentioned above with Magisk 20.1 installed. Running correctly, no modules installed or visible... but if I try to update to 20.3 it bootloops.

So I figured out my problem and fixed my phone. I still find the situation that I ended up in very strange and can't come up with a complete explanation of what happened. But the root issue was that I had a remnant sepolicy.rule from a test module I was playing with on my Pixel's /persist/ partition. Since that particular sepolicy.rule caused a bootloop I was never able to remove it via MagiskManager, so the sepolicy.rule was left on the /persist/ partition and Magisk was trying to apply it on boot. The solution was to re-root using the boot image I mentioned above and remove the file from /persist/.
The issue has been mentioned to TopJohnWu and a fix will likely be included in the next release.

Related

TWRP, System writing, Supersu, Impossible?

I have had my fair share of problems modifying android before but I have never had a phone flat out lie to me and say an operation was successful and actually nothing happened at all.
Have had my nexus 6 for a year or so now. Have had minor issues rooting / modifying marshmallow in the past but I figured out it was all caused by the system partition having basically 0 free space. Made a huge mistake and installed to the latest 7.0 OTA. Wanted to simply enable tethering and edit the thermal config to not shut cores down. Should be as simple as pulling the files, editing them, pushing them back to the phone in twrp with the system partition mounted and thats the end of it right? Wrong.
First of all twrp 3.0.2 refuses to let me touch the system partition without some giant prompt about how its going to make itself stick and offer to root the phone. Simple enough I have seen it in previous versions I say yes as usual except twrp proceedes to immediately spew a bunch of superuser files that do nothing throughout the system partition without asking me if I want root. Dumb but whatever. I mount /system as read write and I go edit and replace my two files like usual (build.prop and thermal config). No matter if I ADB push or use twrps built in file manager it claims the file replacement is successful. Reboot into android and not only have both files not been touched (Verified by adb pull) but the recovery gets overwritten with the factory recovery anyways. (NEVER had issues with twrp sticking on marshmallow. Now after every reboot it gets wiped out)
Second of all if I select yes to twrp mounting system as writable and it does its spewing as I mentioned before then installing SuperSU instantly causes the phone to not boot. Rewrite the boot.img to factory and it boots fine OR Rewrite the clean factory system image and the SuperSU boot works fine. But modifying /system with twrp and then running supersu at the same time is a no go. TWRP is obviously doing something stupid to system that pisses off supersu so undoing twrps mess or uninstalling supersu makes it bootable again.
I dont even want root! Everyone is claiming you need to run "settings put global tether_dun_required 0" as root along with adding the usual "net.tethering.noprovisioning=true" in the build.prop to get native tethering working again! On 6.X only the build.prop edit was needed to get it working.
So long story short. I just want native tethering to work and to tweak my /system/etc/thermal-engine-shamu.conf . Is there anyone here who has done this successfully on nougat? I feel like its all twrps fault but im far too tired and frustrated to try another version tonight.
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Strephon Alkhalikoi said:
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Click to expand...
Click to collapse
It's stated in the op he's using twrp 3.0.2.
Didgeridoohan said:
It's stated in the op he's using twrp 3.0.2.
Click to expand...
Click to collapse
I misread his post then. I wonder if perhaps he is running TWRP via fastboot instead of installing it.
Flashing recovery using "fastboot flash recovery XXX.img"

Strange Magisk installation behaviour

Hi guys.
I'm facing an issue with Magisk (stable and beta) that I never had before. I'm on OP5, PixelExperience, Android Pie (but I've tried also on a Oreo ROM yesterday, not sure if it was stable or beta version of Magisk). Here's the flash routine I do for every single ROM:
- Wipe everything, internal storage included
- Flash ROM
- Flash Magisk
- Boot
In the past few days, Magisk isn't installing MM, don't know why. It always installed MM on every single flash I did in my life, now suddenly it isn't installing it anymore. I haven't changed my flashing "habits", I do the exact steps I wrote above on every single flash (not on updates, of course).
This issue also leads to not being able to install modules from MM, but I can install them via TWRP (I've got the latest blu_spark, I'm decrypted, flashed no_verity_v2 for OP5). When I install modules via MM it says:
! /data/adb/magisk_merge.img mount failed.
I tried re-installing Magisk, using the uninstaller and then first time the stable, then the beta, but they won't installing MM after flashing.
What do you guys think?
Thanks.
EDIT: I've recreated the issue, I've attached the log. I tried 2 different modules, Sysconfig Patcher and Busybox. The first one is installing only via TWRP (via MM it produces the log in the attachments), the second one is istalling via MM correctly.
"update-binary: line 203: make_ext4fs: not found"
Unable to format the .IMG to ext4 it seems so there's no magisk merge image to be mounted
Not entirely sure where to go with that but it could be a start.
Bad version of twrp?
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
Indeed, there's stuff to "fix". I've been working on that for a few days now. I noticed [some] recent ROMs lack a bunch of useful binaries, such as make_ext4fs and resize2fs. So, I'm migrating to Magisk Module Template and relying on Magisk's util_functions.sh for better "future-proof" compatibility.
Didgeridoohan said:
If I understand you correctly, the Busybox module install just fine, no matter if installed through the Manager or TWRP.
Have you tried other modules?
The Sysconfig Patcher module isn't using the official module template, so it's very likely that @VR25 need to fix something in his install script.
Click to expand...
Click to collapse
I tried YTVanced module, downloaded via MM and it installed just fine. So I think that, as VR25 said, the ROMs I've tried these days might have lacked of those utilities. So we might have "solved" this issue.
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Pipodi93 said:
And what about the fact that flashing Magisk from TWRP doesn't install MM? Is it also related to the fact that those ROMs are recent?
Click to expand...
Click to collapse
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Didgeridoohan said:
That happens once in a while, and may very well be ROM related. Fortunately, it's easy to install manually...
Click to expand...
Click to collapse
Yeah, I thought so too. Because when I was on AICP, MM was installed after flashing. My concern was that "mount failed" was related to the fact that MM wasn't installed during the flashing operation, but I'm glad to see that's not the case and my phone isn't cursed. Thank you!

Magisk v17 Failed to Install

I attempted to go from Magisk v16 to Magisk v17 from the app, Install > Patch Boot Image File > Magisk-v17(1700).zip and I get the below .
I opened up Root Checker and it let me know that the device no longer has Root.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
! Installation Failed
Magisk Log File
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.0(17000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
Device Stats
Nexus 6P
Lineage 15.1
TWRP - latest
Any help would be greatly appreciated.
monteie2016 said:
I attempted to go from Magisk v16 to Magisk v17 from the app, Install > Patch Boot Image File > Magisk-v17(1700).zip and I get the below .
I opened up Root Checker and it let me know that the device no longer has Root.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
! Installation Failed
Magisk Log File
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.0(17000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
! Installation failed
Device Stats
Nexus 6P
Lineage 15.1
TWRP - latest
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Happened with me also...i gues the only solution is you have to uninstall mafisk via magisk uninstaller and flash it once again via whatever recovery you are using...i am also using lineage os 15.1 but with RN4....
Happened to me as well. HTC u11, ViperU 1.8.0, Android 7.1.1, TWRP 3.2.2. Tried flashing it though TWRP got a bootloop. Had to revert back to my previous nan which luckily I made yesterday.
I attempted the same, now my galaxy s6 is in a boot loop
Look other posts in this section - you should flash latest uninstaller before Magisk v17 package. It seems that some residues from v16 prevent v17 from installing correctly.
^^^^^^^^^^
how to uninstall magisk completely without custom recoery
Hello Guys
I can not install Magisk v17.1
I delete it complete with the uninstaller
And then flashed again in TWRP, but dont work
Magisk icon is not visible and I can not manually install the Magisk Manager
Pls Help
edkmho said:
how to uninstall magisk completely without custom recoery
Click to expand...
Click to collapse
I had to reflash stock (OTA sideload version, in stock recovery) via adb sideload. Essential phone. Wifi is working now, didn't lose any data.
I'm also having the issue on my OnePlus 5T. I was running v16.0, and when I tried to flash the v17.1 zip in TWRP like usual, but it said zip signature verification failed. I flashed the Magisk uninstaller zip and tried again, but still had the same problem. I've lost root, but all my data is still intact and it never had boot issues.
After using uninstaller in recovery, restart into recovery to flash v17
aydinbahadir88 said:
And then flashed again in TWRP, but dont work
Magisk icon is not visible and I can not manually install the Magisk Manager
Click to expand...
Click to collapse
Do you update from 16.0? If Yes test following:
Download the seperate MagiskManager-v5.9.1.apk
Make sure that you adb is working, connect your phone to computer
Code:
adb devices
must show your phone, if not adb is not proper set
Code:
adb install MagiskManager-v5.9.1.apk
if you get a error message like
the sign with the installed apk has not matsched..aborted
Click to expand...
Click to collapse
the uninstaller not proper delete the old magisk manager
try
Code:
adb uninstall com.topjohnwu.magisk
the result must be an sucess
then again
Code:
adb install MagiskManager-v5.9.1.apk
result must also sucess
Reboot, voiala its done....
You see the Magisk Manager
Does anyone have a working solution?
1.download magisk 17.zip from inside magisk 16
2. uninstall magisk 16 (i do from inside, not twrp)
3. instal magisk 17.zip from twrp
4. open magisk 17 and get notification for downloaded magisk 17.apk
5. download and instal it,
tested by my phone
mi5 Lineage Os 15.1
How I recovered from this on a Pixel 2 XL
I'll chime in with my experience here, as it might save someone else a lot of time if they are at my skill level with this stuff (which is only moderate, I suppose, although I do always get things to work eventually!).
As of yesterday, I had a Pixel 2 XL, rooted with Magisk, and working great. This morning, during the middle of the night, Magisk innocently asks if I want to upgrade to a new version. I was very tired (in fact, I think I was sleeping when my phone buzzed to alert me of the upgrade message) and don't even know how I responded except that it was "yes" to the upgrade part. By the time I'd fully awakened, I had a phone that waw in a boot loop. I went back to sleep, figuring I'd have better luck looking at it after a little rest.
Getting out of the boot loop was easy: I just reinstalled the August 2018 factory image for the phone. However, getting Magisk reinstalled was an adventure. I saw posts that said I should run the Magisk uninstaller, but when I did it just said that Magisk was already uninstalled. And yet, whenever I tried to apply either v16.0 or v17.1, I got errors (error codes 1, 2, and 255 at different times).
Up until this event, I'd always upgraded Magisk by installing it via TWRP. However, that was not working, so I thought I needed to try patching the boot image, something I'd never done before. Because I'd never done it before, it took me a while to understand the steps, which are actually quite simple. This is where I'm hoping I might save someone some time. Basically, my fear was not knowing which file the "boot image" was. Seasoned Android veterans might get a chuckle out of this, and that's fine, but I was looking at the file in the factory image download and basically saw only two image files: bootloader-taimen-tmz20j.img and radio-taimen-g8998-00253-1805232234.img. I was trying to figure out if either of those could be the boot image, and they both seemed pretty big to be a boot image! Finally it dawned on me that the much larger file in the directory was a zip archive (named image-taimen-ppr1.180610.009.zip). I looked inside there, and sure enough, there was a rather small file named boot.img. I was pretty sure that was the "boot image" file!
Here's what I did after that, again just hoping to help anyone who finds themselves in the same predicament I was in: Magisk is broken, root isn't working, and I can't install any of the Magisk *.zip images via TWRP.
- First, I downloaded a copy of Magisk Manager: this version is named MagiskManager-v5.9.1.apk.
- Next, I ran a couple adb commands to send the Magisk Manager apk and the stock boot.img to my phone:
Code:
adb push MagiskManager-v5.9.1.apk /sdcard/Download
adb push boot.img /sdcard/Download
- Next, I installed /sdcard/Download/Magisk-Manager-v5.9.1.apk by nagivating to it (I use ES File Manager) and launching it from there.
- Next I opened Magisk Manager
- Magisk Manager detects that there is a newer version available and asks if I want to upgrade
- I said yes
- I told it that I wanted to patch a boot image
- I chose /sdcard/Download/boot.img as the "unpatched" (stock) boot image
- Magisk Manager churned away for maybe half a minute and then produced a new file called patched_boot.img, saved in the same directory as boot.img.
After that, all I had to do was run these commands:
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
As soon as the phone restarted, I opened Magisk Manager again and it verified that its upgrade was successful, and root began working for me again also.
Like I said, I hope this helps someone else. If not, it's probably good for me to just write it all out anyway.
Cheers,
Sky Captain
_sky.captain_ said:
I'll chime in with my experience here, as it might save someone else a lot of time if they are at my skill level with this stuff (which is only moderate, I suppose, although I do always get things to work eventually!).
As of yesterday, I had a Pixel 2 XL, rooted with Magisk, and working great. This morning, during the middle of the night, Magisk innocently asks if I want to upgrade to a new version. I was very tired (in fact, I think I was sleeping when my phone buzzed to alert me of the upgrade message) and don't even know how I responded except that it was "yes" to the upgrade part. By the time I'd fully awakened, I had a phone that waw in a boot loop. I went back to sleep, figuring I'd have better luck looking at it after a little rest.
Getting out of the boot loop was easy: I just reinstalled the August 2018 factory image for the phone. However, getting Magisk reinstalled was an adventure. I saw posts that said I should run the Magisk uninstaller, but when I did it just said that Magisk was already uninstalled. And yet, whenever I tried to apply either v16.0 or v17.1, I got errors (error codes 1, 2, and 255 at different times).
Up until this event, I'd always upgraded Magisk by installing it via TWRP. However, that was not working, so I thought I needed to try patching the boot image, something I'd never done before. Because I'd never done it before, it took me a while to understand the steps, which are actually quite simple. This is where I'm hoping I might save someone some time. Basically, my fear was not knowing which file the "boot image" was. Seasoned Android veterans might get a chuckle out of this, and that's fine, but I was looking at the file in the factory image download and basically saw only two image files: bootloader-taimen-tmz20j.img and radio-taimen-g8998-00253-1805232234.img. I was trying to figure out if either of those could be the boot imag, and they both seemed pretty big to be a boot image! Finally it dawned on me that the much larger file in the directory was a zip archive (named image-taimen-ppr1.180610.009.zip). I looked inside there, and sure enough, there was a rather small file named boot.img. I was pretty sure that was the "boot image" file!
Here's what I did after that, again just hoping to help anyone who finds themselves in the same predicament I was in: Magisk is broken, root isn't working, and I can't install any of the Magisk *.zip images via TWRP.
- First, I downloaded a copy of Magisk Manager: this version is named MagiskManager-v5.9.1.apk.
- Next, I ran a couple adb commands to send the Magisk Manager apk and the stock boot.img to my phone:
Code:
adb push MagiskManager-v5.9.1.apk /sdcard/Download
adb push boot.img /sdcard/Download
- Next, I installed /sdcard/Download/Magisk-Manager-v5.9.1.apk by nagivating to it (I use ES File Manager) and launching it from there.
- Next I opened Magisk Manager
- Magisk Manager detects that there is a newer version available and asks if I want to upgrade
- I said yes
- I told it that I wanted to patch a boot image
- I chose /sdcard/Download/ as the "unpatched" (stock) boot image
- Magisk Manager churned away for maybe half a minute and then produced a new file called patched_boot.img, saved in the same directory as boot.img.
After that, all I had to do was run these commands:
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot reboot
As soon as the phone restarted, I opened Magisk Manager again and it verified that its upgrade was successful, and root began working for me again also.
Like I said, I hope this helps someone else. If not, it's probably good for me to just write it all out anyway.
Cheers,
Sky Captain
Click to expand...
Click to collapse
I too have a Pixel 2XL but had a much easier upgrade experience. I downloaded the latest version of Magisk files (3 files: MagiskManager-v5.9.1.apk, Magisk-uninstaller-20180901, and Magisk-v17.1 from here https://www.xda-developers.com/magisk-v17-1-android-pie-a-b-support/) and put them on my phone.
Rebooted into recovery TWRP run the Magisk-uninstaller-2018090 file, then ran Magisk-v17.1 rebooted and all worked (thanks to ALL the developers out there!!!)
I'm running rooted Pie (standard google Pie) with Rootchecker, 4.4.153-FlashKernal-Wahoo-v3.06, Greenify, AdAway, and of course Magisk 17.1.
Hope this helps.
akohle said:
After using uninstaller in recovery, restart into recovery to flash v17
Click to expand...
Click to collapse
flashed uninstaller in recovery
flashed v17
rebooted
it worked
If patch boot image is getting failed in magisk latest version v17.1 then enable storage permission for magisk app manually in Device/OS setting. Now patch boot image again, It will get patched successfully.
I
pierro78 said:
flashed uninstaller in recovery
flashed v17
rebooted
it worked
Click to expand...
Click to collapse
OK...im a relative newbie here...first post actually....but Im a bit stuck in a fastboot boot loop
LG G5 tmobile running fulmics
I decided to try this exact process to get my root back by updating Magisk
booted into TWRP through ADB
flashed uninstaller using TWRP
(cleared cache/dalvik)
flashed v 17.1 (not 17) using TWRP
(cleared cache/dalvik)
rebooted
now i'm stuck in fastboot bootloop….can reboot from fastboot but nothing else
any advice would be appreciated!
update: I am able to get to TWRP using reboot command and holding power and volume down. flashed uninstaller wiped cache/dalvik...rebooted into TWRP long way and then installed 17....still fastboot at startup again
Art1mis said:
If patch boot image is getting failed in magisk latest version v17.1 then enable storage permission for magisk app manually in Device/OS setting. Now patch boot image again, It will get patched successfully.
Click to expand...
Click to collapse
many thanks for the tip!!
spent like an hour trying to figure out why my pixel 2 was failing to patch the boot image.
Allowed storage permissions, flashed the patched boot and now im rooted

Android 4.2 and 4.4 Mediatek bootloop after installing Magisk 18.1

Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
UPDATE: For now, if no other solution is found, bootloop can be bypassed by dirty installing the rom again. But it has to be an easier workaround...
We know now that the problem is caused because of two factors merging:
1- Using Magisk.zip installer through custom recovery
2-In the case that the custom recovery CMW/TWRP installed in the phone is very old (for instance, CMW automade for MTK6589X or TWRP 2.5.0).
While installing, Magisk tries to send commands to the custom recovery that cant be understood by it, leaving the installation incomplete after some modifications in /system (read below recovery log).
Acording to the recovery, it seems that Magisk did some modifications without running correctly survival script - Adding addon.d survival script ("Unrecognized option '-Xnodex2oat'") and .zip installer is not designed to revert actions in this case.
Also, Magisk couldn't reach the boot modification step, so boot is not damaged, therefore workarounds for restoring boot won't work.
Using Magisk Unistaller.zip is also not possible as the uninstaller is mainly designed for boot backup restoration, and again, this is not the case.
Currently needed: Find what's wrong in system due to the incomplete Magisk installation to revert it back to the original state (before faulty magisk.zip installation).
Recovery log:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
up!
I' also having the same problem. My Samsung J2 Prime stuck at logo after updating to 18.1. Any tips on how to fix it without resetting my phone? Thanks.
Update: Bootloop fixed. I used TWRP to restore boot image. I then update Magisk by flashing zip file from TWRP. Everything went back to normal. Hope this help.
trol_sg said:
Hello everybody.
I've read that 18.1 supports 4.2+ so I've tried to install in two MTK6589T devices I've. One running 4.2, the other running 4.4
CMW/TWRP gave an error mounting system, so I mounted system manually and it started flashing. Firstly it detected old root installed and disabled the old root. But when it tried to find the boot, installation was aborted because installator claims cannot find the boot on both phones.
Then I though, okay, lets reboot back to android, I will try to install a few days later, maybe its buggy now, but both phones cannot boot.
I can easily fix them by flashing rom again I guess, but I would like to know where's the issue and also post it for more people could face the same problem.
Any idea where's the problem/how to fix without rom reflashing? I've tried magisk uninstaller but after mounting system in recovery it is also giving error.
Thanks
Click to expand...
Click to collapse
If you have a backup of your boot image, you can just restore it using TWRP. But in case that you have no backup of boot image, you can try to get boot image from the internet and restoring using it. In my case, this is what I did.
1. Go to TWRP and then make backup of boot image of the faulty phone*. (Folder 1)
2. I used another J2 prime to create a boot image backup. (Folder 2)
3. Once that is done, copy and replace the files inside the Folder 2 into Folder 1.
4. Reboot to TWRP again then use that to restore the boot image on my stuck J2.
Tips: make backup in SD card so you can easily swap it in between the bad and good phone.
*This is to create a folder of the backup file. I did tried to directly copy and paste the backup boot image file from another good phone but TWRP didn't detect it. So this is the workaround that I come with. And it worked for me.
Thanks for your answer but I doubt your case is mine. Your device is much newer than mine and according to your comment, you've sucesfully installed previous version of Magisk without issues. This is not a problem while updating, as Magisk v. earlier than 18.1 was not compatible with android 4.2+. I think Magisk is not compatible with MT6589T even if they run 4.2 or 4.4.
I think that it cannot be a boot problem as TWRP/CWM displayed msg 'Boot cannot be found' while installing Magisk, so that I don't think boot was replaced or modified in any ways. Moreover, the bootloop is not in the boot loading, as phone can pass boot image without any problem, but it is stuck in android loading image. I'm thinking in some script or root modification that Magisk did before trying to unpack the boot, however I'm not that deep into the Magisk install to find the proper workaround.
I can restore boot backup and also I can take boot file from the original rom and flash, because in Mediatek-based devices, boot.img is inside de zip, but I dont think it will solve the problem. Anyhow I'll get back ASAP with the answer.
Any more ideas??
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
trol_sg said:
Nothing, boot/uboot restoration or flashing again just the boot won't fix the problem, so it's something that Magisk installator touch in /system or /data I guess, but what?
Click to expand...
Click to collapse
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Ato09 said:
Have you read/tried this?
didgeridoohan(dot)com/magisk/MagiskIssues
Click to expand...
Click to collapse
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Here I attach recovery.log if someone is interested to see the detailed problem.
Also, here below I attach the lines concerning the installation. All other is uninstallation tries and so on:
************************
* Magisk v18.1 Installer
************************
- Mounting /system, /vendor
- Target image: /dev/bootimg
- Device platform: arm
- Removing system installed root
- Constructing environment
- Adding addon.d survival script
Unrecognized option '-Xnodex2oat'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all,full}
-Xnoquithandler
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-XX:+DisableExplicitGC
-X[no]genregmap
-Xverifyopt:[no]checkmon
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitcodecachesize:decimalvalueofkbytes
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitclass:classname[,classname]*
-Xjitoffsetffset[,offset]
-Xjitconfig:filename
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
-Xjitsuspendpoll
Configured with: debugger profiler hprof jit(armv7-a-neon) smp show_exception=1
Failed to initialize runtime (check log for details)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/bootimg]
No boot image magic found!
! Unable to unpack boot image
- Unmounting partitions
E:Error executing updater binary in zip '/sdcard/Magisk-v18.1.zip'
Error flashing zip '/sdcard/Magisk-v18.1.zip'
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Didgeridoohan said:
@trol_sg I'm gonna guess it's got to do with the absolutely ancient TWRP you're using. It just can't handle everything that the Magisk installation script is trying to do...
Your best bet (if Magisk will work at all on your device) is to patch the boot image with the Magisk Manager and then flash the patched image manually. There are new and shiny installation instructions available here: https://topjohnwu.github.io/Magisk/
Click to expand...
Click to collapse
Thank you so much for your answer. So it's the recovery, but can't find newer ones, sadly. Too old phones I know, but just curious if I could make Magisk working on them, lol.
I was going into the boot modification manually right now, but in order to patch the boot I need manager installed first, and phone couldn't boot so I did dirty flash of the rom to be able to boot into it again.
Lets see what happens then. I'll be right back.
Anyhow, this is not a solution to fix the problem of bootloop that I am requesting help in case someone could face the same and did not make a backup of the phone and didn't want to make dirty re-flash. Any idea?
Update: After I did dirty flash of the rom, and now Jiayu g3s android 4.4 booted.
UPDATE: So, after patching manually boot and installing (using restore in TWRP 2.5 as image flash is not yet implemented AFAIK), phone booted and yes Magisk is working.
Magisk installation .zip through a very old recovery is making the bootloop. So that, a thing learnt now.
But, for other people facing this bootloop, can we do a research to find what magisk.zip did to the phones to leave them in bootloop? Maybe we can revert without rom flashing easily if we knew what's the issue...
Thanks in advance!
Doing a bit more tests I found that magisk.zip did something in /system so that it is left in bootloop, but still no idea why/whats causing that...
There are delay complete boot like 4 5 second in j7 prime. I didn't love this version
any more help?? up!!
trol_sg said:
Yes, I've read them before I made the post. I've also looked for a solution in some of the threads and using search, but couldn't find a way.
Click to expand...
Click to collapse
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Ato09 said:
Try this.
Quote:
Originally Posted by void74
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
Quote:
Originally Posted by Mangraviti
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
-------------
Original post. https://forum.xda-developers.com/apps/magisk/bootloop-magisk-update-t3836904
Hope it help.
Click to expand...
Click to collapse
Hello, thanks
This method won't work in my case as in the step:
- installed magisk uninstall = gives error
Note 5 is much newer phone with a recent recovery TWRP that allows all Magisk.zips commands, but unluckyly not this case.
Also, this method is for wrong boot installation/damaged boot. In my case what Magisk damage is /system, not boot.
I wish it could be boot, because that is very easy to fix (flashing through fastboot/SP Flash tools in the case of MTK, recovering boot twrp "backup" even if you didn't make backup...) as you mentioned.
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Main post updated with all thread information. Up!
Nothing?? Up!!
trol_sg said:
Hope someone have a great idea to revert system to origin, then we could post the solution for those who would like to install Magisk in 4.2+ old phones, and instead of doing boot flash manually, they try to flash magisk.zip and they got bootloop.
Click to expand...
Click to collapse
The only part of the Magisk installation that actually touches /system is if it installs the addon.d survival script. The log you posted earlier shows that it's trying to do this, for some reason, and failiing. I'd start looking there...

Is there a guide on updating to the newest firmware and Magisk

Fairly newbie user here. I'm looking for a guide that lists how to upgrade the P5 to a new firmware and keep Magisk and all of that. I've looked at the thread below and it is good for getting started up in the beginning, but I'm not following how it works for a new firmware.
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Like how do I flash the new February firmware onto my phone?
Do I then copy the boot.img to the P5 and patch it with Magisk?
Then do I copy the patched boot.img back to my PC and flash it back onto the P5?
Are there are new step or process for unlocking SafetyNet?
I'm just very confused and would appreciate something simple and basic to follow, please.
Thanks!
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
You can bypass safetynet perfectly with hiddencore module for xposed.
HiddenCore Module | Xposed Module Repository
repo.xposed.info
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
hanni2301 said:
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
hanni2301 said:
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
I have tried few years ago, in some previous version of android, instead of running flash-all.bat, I flash each image individually, (fastboot flash bootloader..., fastboot flash boot..., fastboot flash recovery.... etc. ). If I took the shortcut of not flashing the original boot image first and then the patched one, but flash the patched boot directly, then the phone run into a bootloop.
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
VD171 said:
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
Click to expand...
Click to collapse
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Ewto16 said:
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Click to expand...
Click to collapse
Next time, don't flash the factory image. Sideload the OTA.zip instead. That way you won't lose any of that.
Sideload the OTA, flash the patched boot.img (the boot.img you need to get from the factory image though), and you won't lose Magisk, your modules, or your root settings.
I used to do the same. Edit out the -w flag from the flash-all and re- setup my phone. Sideloading the OTA is easier and quicker in the end.
Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
1. Yes
3. Edit the flash-all.bat file with any editor, e.g. notepad in windows, you will see -w near the end of the file, remove it, then save and run the file. You must make sure the -w is removed, otherwise all the data will be wiped
4. To boot into bootloader: adb reboot bootloader
To flash the patched boot image: fastboot flash boot magisk_ patched.img (the file name changes every time, just use the one you have when you patch the boot image)
It's easier to replace the "-w" with "--skip-reboot" (first one is double dashes). The phone won't reboot when the image flashing is complete so you can immediately re-flash the patched boot img.
This youtube video is great to follow and has clear step by step guide.
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Ewto16 said:
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Click to expand...
Click to collapse
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
swangjang said:
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
Click to expand...
Click to collapse
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Ewto16 said:
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Click to expand...
Click to collapse
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
swangjang said:
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
Click to expand...
Click to collapse
Interesting....I thought those were one and the same. Thanks for the tip. I'll give that a try.
I'd still like to get GPay working again though.
VD171 said:
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
Click to expand...
Click to collapse
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
hanni2301 said:
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
Click to expand...
Click to collapse
Grow up, my friend.
Anything can changes from device to device.

Categories

Resources