So i find the pixel module in the magisk manager and just intstall and reboot.
i am stuck at the pulsating samsung logo and met with a sequences of vibrations i never got before and the phone does not boot. I can however get back into twrp by turning off my phone and doing the usual twrp boot sequence.
i have no idea how to fix it.
The only thing i have tried is going into file manager and removing the pixel launcher zip in the magisk manager folder, and then the whole magisk manager folder I may have made things worse.
Edit: Now i deleted magisk.img and the phone boots but systemui and com.android.phone keep crashing and the phone is in effect unusable
What are my options?
Thank you for your time
Try magisk uninstaller.zip then install magisk again and superuser through twrp
Related
Hi, I just dirty flashed my phone through OTA from OB5 to OB6. I currently can't boot into my phone, but recovery and everything works.
I'm using twrp 3.2.1.0 codeworx. I can boot into my lockscreen but the moment it loads it says "Shutting down". If I install Magisk 16.0 it just tries to boot, then fails and jumps to recovery.
At least my data isn't encrypted anymore, but what can I do about this? When I try to sideload the OB5 ROM it says can't read zip.
Also it's interesting how my recovery gets reset every time that happens.
From my knowledge you should make clean flash as android 8.0 and 8.1 are different versions
You didn't removed all the overlays from substratum, navigate with twrp's file manager into /data/system and delete overlays.xml
SventraPopizz said:
You didn't removed all the overlays from substratum, navigate with twrp's file manager into /data/system and delete overlays.xml
Click to expand...
Click to collapse
Thanks for the suggestion. I also feel a feeling that it's substratum because I made the mistake of updating with layers still installed. I tried flashing the substratum rescue zip, both legacy and non-legacy, and also deleting the file as you suggested but I'm still getting that immediate "shutting down" error.
chazarss said:
From my knowledge you should make clean flash as android 8.0 and 8.1 are different versions
Click to expand...
Click to collapse
For my personal experience, I took the OTA and had no problems rebooting. I'm also fully stock with no root or custom recovery; I don't know if that affected my flash and reboot. I bought my OP5 used from Swappa. When I got it, I clean flashed the OB5 and then today I took the OTA for OB6.
I was on ob05, twrp 8.71. Received ota, full zip, on the phone. Dirty flash workt fine for me. Phone booted ok. Of course, recovery was gone. Reflash recovery. Reboot to recovery. Flash Magisk 16. All ok.
Bootloop was caused by https://forum.xda-developers.com/oneplus-5/themes/op5-oos-oreo-official-fix-blue-3rd-t3727238/ for me. After disabling the module with https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 it's booting properly
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
MineMasterHD said:
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
Click to expand...
Click to collapse
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Drkmatr1984 said:
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Click to expand...
Click to collapse
I also have a Moto G5 plus and when I tried to reboot it a second time it was still stuck in its boot loop so I had to enter TWRP to flash the uninstall and if I try to install Xposed via Magisk I have to factory reset, I don't think it's me ROM because it's the same as a stock ROM (had to install the ROM because the one it came with got corrupted or something when I tried to install Xposed where I still had the boot loop problem). I am running 8.1.0 Oreo.
I think a lot of my problem was i was using a sprint variant also. I think a lot of other users are using the verizon/t-mobile variants. I never really did get xposed to work properly on oreo on the sprint variant of this phone no matter what i tried.
Any news on this issue?
I just updated to 8.1 and would like to get xposed up and running like I had it on Nougat. Has there been any fixes yet to this. Thanks to anyone for a reply.
I get bootloop when I install magisk & xposed.
I am using Xposed since months
Working fine
One thing you is that we've to do soft reboot instead of regular reboot
Hello,
i`m on Stock Samsung ROM and rooted with Magisk.
Today i`ve got a message from Magisk Manager that an update is available.
Magisk Manager showed me that there were no root installed.
I started TWRP, flashed latest Magisk (18.1) and rebooted. since then i`m Stuck at the flashing Samsung Logo.
I can start Recovery and i tried Magisk uninstaller but then i ran into Boot Loop. Flashed Magisk again and still stuck at Bootscreen.
What can i do here?
R3van said:
Hello,
i`m on Stock Samsung ROM and rooted with Magisk.
Today i`ve got a message from Magisk Manager that an update is available.
Magisk Manager showed me that there were no root installed.
I started TWRP, flashed latest Magisk (18.1) and rebooted. since then i`m Stuck at the flashing Samsung Logo.
I can start Recovery and i tried Magisk uninstaller but then i ran into Boot Loop. Flashed Magisk again and still stuck at Bootscreen.
What can i do here?
Click to expand...
Click to collapse
In twrp go to wipe and select format data, copy magisk to SD card or internal after wipe, flash magisk. Then it should boot
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.
I installed a module in edxposed that caused a bootloop.
To fix i rebooted to twrp recovery, mounted everything, went to advanced, file manager, located folder edXp in data/adb/edxp and renamed. Rebooted went to edxposed manager deleted problem module and rebooted to recovery. Renamed above folder back to normal and rebooted as normal with no issue. Hope this works.
Oneplus 6t 10.3.4