Database Develop

Blackscreen after magisk update

Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint

yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.

EuEra said:
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
Click to expand...
Click to collapse
That solved my issue, didn't realize that I really bricked my device. Sadly it wiped my data also!
Thanks for your advice!

I've experienced this about 3 times over the last 4 months, and had to restore a full backup each time. Basically afraid to do anything with Magisk at this point. This really needs to be fixed.

It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.

Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
I did that when i switched from official to open beta, and everything went fine, then i installed a module, rebooted and got blackscreen again

Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
It's not the kernel, the black screen has occurred twice when just installing a module with no modifications to /boot.

dre-z said:
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
Click to expand...
Click to collapse
Fix for me was to boot twrp, manually wipe system, data, caches etc (NOT internal storage box), then clean install the OS in twrp. Keeps your data and encryption then.

Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185

I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?

Didgeridoohan said:
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Click to expand...
Click to collapse
Nope, I've had this happen with multiple modules, including App Systemizer, ad-free YouTube, and OP3/T channel bonding enabler. Based on the file size changes in magisk.img, I legitimately think that the linked GitHub issue is the root cause. I think the only consistent repro is to flash different versions of modules while rebooting repeatedly.

Problem might be corrupted magisk.img during resize.

vemacs said:
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
Click to expand...
Click to collapse
I had the same issue when trying to install xposed 87.1 through MagiskManager (black screen and repeated vibration).
On my J5 I just removed the battery and booted into twrp, then I uninstalled magisk with the uninstall-zip, wiped dalvik an cache, rebooted once and everything works.
I reinstalled magisk in twrp and installed xposed 87.0 through the material xposed-installer and everything works.
No data loss.

The issue on GitHub was closed with a comment saying that it's likely fixed in latest Magisk (13.1). FWIW I haven't seen it occur after running 13 beta for a while.

My op3 was bricked again today after the update. Funny thing is, this time I had not installed any module. So the problem doesn't seem to be fixed.

pls someone should help me i tried to root my android v10 infinix note8i with magisk patch boot img file using adb fastboot when i tranfer the file and reboot the phone is not booting and not gettig into recovery mode, just blank screen when a turn on pls help me out with solution

same but my problem is kind of stupid because someone rooted my phone in another way and magisk says it is installed and needs updating but it is actually not and the biggest problem is when i unroot my phone the stupid rmm locks gets enabled and boom i can't open twrp recovery because it is not an offical binary so i got stuck there i flashed a stock rom got it fixed but i still can't do it

WiFi problems caused by Magisk ?

Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11

cl0g said:
Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
Click to expand...
Click to collapse
Remove all modules and reboot into recovery.
Wipe caches and reboot.
I have found that I can end up with WiFi, Bluetooth, SIM issue if something happens with the modules.
Before I figured out what it was, I was re-installing the ROM, etc.
Try just deleting the modules and wiping the caches and rebooting.

@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.

cl0g said:
@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
I actually did read the whole post and was offering a solution that DID NOT require re-installing the ROM.
I'm not 100% sure why the problem persist but I have seen it affect Bluetooth, Wireless and SIM recognition.
Typically it happens after a reboot. Wiping the cache on my phone causes it more than 50% of the time if I don't disable modules first.
I don't know why it happens but you are right, removing Magisk does not solve the problem.
There is something corrupted in the data partition and the only way to clean that up is to remove the modules and wipe the cache or do what you proposed.

Nevermind

I recently had the same problem. I'm currently trying to fix it without reinstalling. I've uninstalled all modules, cleared both caches and still no wifi and I'm getting random crashes. Has anyone found fix a reliable fix?
While posting, I tried resetting my network and everything started working again. If this happens again, I'll try that first.
BTW
Also, it happened after a failed installation of Crossfire and Tethering, both thru Magisk. Tethering actually installed but after the reboot, I've got no wifi.

I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael

mellus said:
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael
Click to expand...
Click to collapse
Ugh. I'm having the same issues after upgrading to canary channel Magisk 20.4 on my Razer Phone 2. My WiFi was rock solid on the previous version, but for some reason my WiFi now flashes on and off like a strobe. Weirdly, it doesn't seem to have the issue at my house, but it constantly craps the bed at my work. The work connection is 5Ghz and my home one is 2.4Ghz, so that could be a difference. However, before my attempted upgrade, both worked perfectly.
I tried uninstalling my Magisk modules, flashing the Razer stock boot image, wiped Dalvik cache, flashed Arter/TWRP boot image, Arter kernel zip, Magisk 20.3 stable and reactivating modules. No change at all. WiFi is still garbage.
Are you telling me I'm going to have to flash the entire stock image and wipe my phone to get back full functionality?

im having the same problem, on miui i tried tp downrage magisk, that worked. currebtly searchin best way to downrage cause i forgot what i did. but if anyone stuck at this problem:
Without data wiping (luck method):
Remove modules
Reboot into recovery
wipe caches
reboot
done
Downrage magisk (maybe not fix):
Uninstall ALL modules
Delete Magisk from the app
flash downrage magisk
(eg. uninstall 24.1, install 23.0)
wipe caches
reboot
done
Data wiping (i forgot about should we flash magisk via magisk app with recovery mod on, if this dont work try enabling recovery mode):
Just Re-install Magisk via recovery
Clean everything BUT leave boot not wiped
flash rom WITHOUT boot
let it 10-30 minutes booting
go to recovery
flash rom's stock boot
reboot
finish rom's installation
install MAGISK APP
confirm additional installation
reboot
done

Flashing nightmare

So here are a few things I have been through in the past 48 hours:
I flashed a custom ROM (FreedomOS) for the 3T. Could not get OK Google to work and it is essential to me especially when driving. Other people had mentioned every custom ROM was like this at the moment so I made the switch back to factory. This is where the hell begins. I wanted to try out Magisk so I could play Pokemon GO and use Android Pay, and I thought "oh what a perfect time to do just that". 4 hours of work and the SafetyNet was still tripping, only to find out I needed Magisk 13.0, which is incompatible with the OP3T boot image. Now, that could have been because I installed SuperSU prior and that patches the boot image but I had been through enough to the point of just going stock with SuperSU only. So about 10 dirty flashes later and a few hours of waiting for TWRP to load (F2FS can suck my @#$*), I find out that if you don't want to lost your data partition, there is only one very specific way to install SuperSU.
1) Wipe system and caches
2)Install OOS full rom
3)Boot into OS
4)Reflash TWRP (because OOS removes it)
5)Flash SuperSU
6)Boot into OS again
7)THEN, and only THEN can you install additional things such as ARISE or custom fonts
It appears after you flash the factory ROM through TWRP, TWRP loses all commands. So anything flashed after that doesn't actually do anything. I thought maybe it was because the new recovery is there and so maybe TWRP just needed to be reflashed before the OS was even booted, that however, resulted in a beautiful slew of corrupted fonts, no root access and broken hardware keys (even the power button). So please, learn from this XDA users, as I have the hard way. Now I'm off to go change F2FS to EXT4, fun stuff.
EDIT: On top of everything I just said, it seems none of the SuperSU zips are working now. Does not affect my phone whatsoever. It's almost like it isn't mounting /system...
EDIT 2: Great. Rooting now bootloops me and the logcat is saying AtCmdFwd service errors and BindNDK sensor server unavailable. I'm going back to FreedomOS and will just suffer from never having OK Google again.
EDIT 3: FreedomOS no longer even starts booting. Stuck at bootloader logo. Guess I'm flashing stock OOS unrooted for now. Going to have to deal with ugly default fonts and crappy audio

Try blusparks twrp for OnePlus 3t.. that fixed a lot of my issues with flashing, instead of supersu try magisk instead.
Install twrp - OOS - Magisk - Kernel - what ever else.. but see if it boots. If not, try holding the power button for 12-15 seconds until the screen goes black but the notification led turn red.. plug your phone into the computer and do a unbrick from there with the msm tool.. once it all boots, flash a custom rom over the stock rom and then factory reset from there, I'm just throwing ideas out there.

1. Factory reset.
2. Install official OOS.
3. Reboot to recovery.
4. Install TWRP.
5. Install Magisk, custom kernel, debloater etc.
6. Reboot to OOS.
When upgrading to newer OOS version, skip factory reset. I never wipe caches and everything works. If safety net fails, check that hide is enabled on Magisk settings. If still failing, use Universal SafetyNet Fix.
Forget SuperSu, Magisk does same thing. And with Magisk you can play PoGo. Forget EXT4, it doesn't give you anything, it's going to be history.

Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.

Solved
xKroniK13x said:
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Click to expand...
Click to collapse
Ok, I will eventually try blu_sparks TWRP (that was the plan anyways), but I am back in working order. So Magisk did not bootloop my device, and v13 works on OOS. It wasn't working on FreedomOS but it even passes SafetyNet on OOS. I have ARISE and Dolby installed and couldn't be more satisfied. Did not have to wipe /data, it's like the whole thing never even happened. I will likely change to EXT4 as soon as I get the chance to backup my data partition, I haven't seen any benefit to F2FS whatsoever. Appreciate the tips, XDA rocks!
EDIT: Still takes forever to boot blu_spark TWRP but eh, I'll keep it. Will update when switch to EXT4, only reason to switch

I do the flashing in a rude way
1. Flash OOS from TWRP.
2. Flash magisk, arise, etc..
3. Reboot
4. Boot into recovery, flash any custom kernel etc..
Changing to ext4 is not required, if you are on OOS. f2fs is way better in performance over ext4 for the stock/freedom.
Sent from my OnePlus 3T using Tapatalk

PP3 Compatibility?

Magisk worked fine on the Android P PP2 beta. Just upgraded to the new PP3 and Magisk 16.4 doesn't seem to work. It flashes fine in TWRP, but Magisk Manager says it's not installed. Just want to check if others are experiencing the same before I assume it's just me and start troubleshooting.
I'm running a Pixel XL.

Same in my pixel 2 XL
I tried patching the boot.img and I got an error

I flashed 16.4 on my Pixel with PP3 and it installed fine. Root seems to work as expected, but modules dont install.

Having the s ame issue. Can't unpack and patch boot.img.

I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.

SirLoinOfBeef said:
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
Click to expand...
Click to collapse
I flashed 16.4 and for some reason worked... but only couple of minutes then suddenly root dissapeared :/

For me works with no problems.
I disabled all modules (just to avoid problems), dirty flashed dp3 over dp2, removed lockscreen password (again, just to avoid possible problems with twrp).
Booted twrp img, then in recovery:
- flashed latest twrp.zip
- rebooted recovery
- I flashed Flash Kernel just because I like it
- Straight after magisk 16.4
- rebooted.
Then I re-enabled all modules and set the password back. Super smooth and zero problems, root survives every reboot, no crashes or freezes of any kind. Also if I download modules they all works.

Still can't get it installed. I am trying to patch the boot.img file via Magisk Manager.
I get:
Code:
- Device platform: arm64-v8a
- Extracting files Failed!
! Installation failed

Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.

djuniah said:
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
Click to expand...
Click to collapse
I assume you installed through TWRP?

joderme said:
I assume you installed through TWRP?
Click to expand...
Click to collapse
Yes, i flashed through TWRP. I basically have done the same thing TENN3R mentioned above minus a kernel install. I've tried it a few times now with no luck. Pixel XL btw.

Soft bricked....

So I finally went ahead unlocking the BL & rooted my Mi9Tpro, using the program by Maunofrio.
So far, so good. Installed twrp from within the program, along with some kind of superSU.
I installed some apps needing root, but they complained over an outdated supersu, so
I then installed the superSU by chainfire. First 2.82 wich wouldn't update the binaries.
Then the 2.79 version, that was said to be more bug free.. It didn't want to update the
binaries either, the normal way. So I then chose the other option (to DL by twrp).
Now my phone won't boot past the boot screen. I can start both fastboot and
recovery mode (twrp). Would anyone be kind and tell me how to solve this?
I just don't know how to proceed (so I guess I shouldn't have fiddled at all).

Just flash Magisk for root.
That will work 4sure.

Televinken said:
So I finally went ahead unlocking the BL & rooted my Mi9Tpro, using the program by Maunofrio.
So far, so good. Installed twrp from within the program, along with some kind of superSU.
I installed some apps needing root, but they complained over an outdated supersu, so
I then installed the superSU by chainfire. First 2.82 wich wouldn't update the binaries.
Then the 2.79 version, that was said to be more bug free.. It didn't want to update the
binaries either, the normal way. So I then chose the other option (to DL by twrp).
Now my phone won't boot past the boot screen. I can start both fastboot and
recovery mode (twrp). Would anyone be kind and tell me how to solve this?
I just don't know how to proceed (so I guess I shouldn't have fiddled at all).
Click to expand...
Click to collapse
Download and flash rom from this thread. (For recovery, not fastboot.)
https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647

Thanx, fellows!
I tried reflashing Magisk once more, & it did the trick.
:good::silly: