Database Users

[solved] Stuck on 1+ logo on boot after flashing Magisk, works perfectly without

Spoiler: Culprit was App Systemizer.
I've had Magisk on my OP5 (128) for some time, and had the most common modules installed (can't get the list currently), but when I rebooted the phone this morning to install AllStream (dlna streaming app), the phone got stuck on the 1+ logo screen, that shows before the boot animation. I let it run for around 15 minutes but it was still stuck.
I rebooted into fastboot (recovery didn't work) and did
Code:
fastboot boot twrp-cheeseburger.img
to get into TWRP, and I reflashed the zip of the latest OOS (4.5.8) (of course, wiped caches beforehand). I rebooted and it worked (no root, of course).
So I rebooted into TWRP and flashed a freshly downloaded Magisk 13.3 zip, rebooted, and then it got stuck on the 1+ logo again. Flashed OOS zip, and it worked again (writing from the phone right now).
TL;DR: OP5 128 with Magisk & TWRP works perfectly. And then one day, book, stuck on logo at boot
Flashed latest OOS zip, works. Flash Magisk zip, stuck at boot again. Flashed OOS again, works.
In case of a Magisk module is responsible for that, how can I remove modules without actually installing Magisk?

I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5

Try just installing the magisk manager apk but without installing magisk root. Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.

Wechy77 said:
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Click to expand...
Click to collapse
You don't need to flash the twrp image on every update.

As I said, Magisk has been working perfectly for weeks, it's just that when I random rebooted my phone it didn't boot correctly.
Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Click to expand...
Click to collapse
If Magisk is not installed, Magisk Manager doesn't have the Modules tab.
You don't need to flash the twrp image on every update.
Click to expand...
Click to collapse
I do. Stock recovery is restored every time I flash an update.
I am quite sure the problem comes from a module and not from Magisk itself, since it was working before. But I can only remove modules if Magisk is installed.

Quote from my reply on the other thread
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse

I'm having the same problem, look here: https://forum.xda-developers.com/oneplus-5/help/magisk-modules-t3651558
I suppose the magisk's modules stay installed in the background and when we flash it again, the phone bootloops.
I had to use SuperSU for now until I understand what's happening.

Need some help - Strange OP6T storage issues after flash

Hello, I have a T-Mobile 6T which thanks to the XDA thread about bypassing T-mobile, is running the international firmware so I didn't have to kiss their butt trying to unlock the bootloader. Yesterday I decided to try the Resurrection Remix rom since it is unclear whether the Lineage 16 rom supports the in-display fingerprint reader, and I am too busy at work and too lazy to read the entire thread to see if it does.
I followed the instructions and updated my OxyOS to the latest .15 release via TWRP which I also updated to the latest version via OTG using a USB drive because I was unable to unencrypt using the older Blu-Spark TWRP version I had installed. After the OxyOS update (on both partitions) I flashed TWRP again, rebooted to recovery and installed Pico Gapps.
I found the Resurrection Remix rom to be very buggy and I hate the way the in-display biometric works (very slow and I don't like the paw print used as fingerprint placement). Anyway I started installing apps and after 4 apps installed, it says there is no space left in storage.
Nothing will update, and when I try to check storage with any file explorer it says "access denied" or just won't load. I've tried everything. Wiped the data and did factory reset, then flashed stock rom again and same issue. What am I doing wrong?

That looks like a messed up flash. And is pretty common. Considering that A/B is still new and everyone has his own method of flashing. So assuming you can make it back to latest Stock OOS (9.0.15 right now). If you dunno how to then simple reboot to recovery, flash OOS ZIP and then TWRP. Again Reboot to Recovery from within TWRP (Reboot -> Recovery) and again flash OOS ZIP and TWRP Installer. For TWRP I recommend you to grab the latest one (3.3.1-6 as of now). Once flashed, Format Data (Wipe -> Format Data -> YES) and Reboot. Wait for it to boot up. Now you should be on Stable Stock OOS with TWRP Installed.
Now Download ROM of your Choice (RR, LOS, Bootleggers, whatever). You will also need the latest TWRP Installer (same as above) and Gapps (Nano/ Stock Recommended) and Magisk if you want to Root. Reboot to Recovery, flash ROM ZIP and TWRP Installer ZIP. Wait for it to Finish. Reboot to Recovery. Once in TWRP, again flash ROM and TWRP Installer. Once done, again. Reboot to Recovery from Within TWRP. (Read above on how to). Now, flash Gapps. Magisk if you want to Root. Once done, again do a Format Data. Reboot and be patient for ROM to boot. And then tell me wether this works or Not. Good Luck.

Problems with MIUI v11.0.4 and TWRP/Magisk

Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder

coder111 said:
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
Click to expand...
Click to collapse
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both

Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
zgfg said:
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Click to expand...
Click to collapse

coder111 said:
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
Click to expand...
Click to collapse
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP: https://mega.nz/#F!hllnSIpA!amAG8moMYW_tG8r731Tzgg

Thanks for your help.
I tried the thing with Magisk Manager & boot image file, and it worked. I can live with stock recovery for now. I just needed root.
You saved me quite a bit of hassle. Thanks again.
zgfg said:
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP:
Click to expand...
Click to collapse

[FIX] Flashlight and Camera not working after updating rooted 5T to OOS 10.0.0

After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Sent from my ONEPLUS A5010 using Tapatalk

nadiration said:
After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Click to expand...
Click to collapse
Can I give link for the ROM you flash?

zhukry said:
Can I give link for the ROM you flash?
Click to expand...
Click to collapse
[emoji1428] https://otafsg1.h2os.com/patch/amaz...ygen_43_OTA_067_all_2005130057_6b923fb89f.zip
Sent from my ONEPLUS A5010 using Tapatalk

Thanks for this! The same thing happened to me. You saved me hours of troubleshooting!

Thanks VoltaGe86 - been driving me mad for a week now and your advice has solved all my camera & flashlight problems AND YouTube and Tasker not connecting.
Appreciate your post!

i know i am late but
if anyone else is facing this problem then try installing open camera and try going to stock rom(old one) do rom update with stock recovery

I've been experiencing the same loss of camera and torch/flashlight after upgraded my Oneplus 5T to the latest firmware (10.0.0/10.0.1).
It was not solved by using magisk uninstaller and downgrading.
Additionally, the phone will not auto upgrade to new releases, whatever rom I install it always insists 'Your system is up to date'.
After wasting far too many hours I've found that the camera works on stock roms up to Oxygen 5.1.7 (Android 8 Oreo), but stops working when flashing the next update: Oxygen 9.0.0 (Android 9 Pie).
I've addtionally tried unbricking the phone using dumpling_43_O.36_180613_unlocked.7z and have attempted to upgrade with OEM Unlocking turned off.
Any ideas as to what might be the cause would be super welcome!
I'm wondering if the underlying paritioning could be damaged in some way?

TWRP 3.5 on OnePlus 6T?

Title says it all. I've recently tried to install TWRP on 6T (latest OOS) but little to no avail. I was wondering has anyone have success with upgrading from 3.4 to 3.5 while keeping data? and if you have could you guide me into the steps that you have done to fully get the TWRP working?

No issues here, booted to twrp and flashed latest twrp installer, then magisk if you want root

@Huskied I used the themed One Plus TWRP located here on my Oneplus 6T. https://forum.xda-developers.com/t/...-twrp-by-acuicultor-morphine1.3847752/page-10
It's on the last page if interested. I'm currently using v3.5.2-9 from there. Zero issues installing it on my end.
Flash TWRP installer zip through TWRP on your device then reboot. You should have TWRP installed then.
On my global Oneplus 6t .
Rom install w/TWRP install:
Flash OOS 10.3.9
Flash rom (with gapps included as example)
Flash TWRP installer zip
Flash finalize
Reboot recovery
Flash magisk 22.1 zip
Format data (swipe yes) wipes everything!
Reboot system.
If you just want TWRP then just install installer zip and if you want root install magisk zip afterwards then reboot. Should be good then.
(Edit)