OK, so I'll start out by saying that up until a few days ago I was quite happily running Magisk 21.4 with just Systemless Hosts, Magiskhide and Universal Safetynet Fix, nothing else. I got the message saying v22 was available so I went ahead and updated and as many people have reported I got a bootloop. After trying a few buttonpress options I got my phone to boot but I found that none of the above modules were loaded - I since found out I had inadvertently found the 'safe mode' option for booting with all modules disabled.
I restarted the phone and it booted with no problem. Checked for root, all good. Adblocker was working, all good. Checked MagiskHide and found it was disabled. Re-enabled it and restarted the phone and got into a bootloop. Used safe mode to get it started and went through the same process but whenever I enabled MagiskHide I would get into a bootloop. I then tried adding the Universal Safetnet Fix, rebooted and got into a bootloop. Went to safe mode etc, etc...
After countless bootloops I decided to remove Magisk completely and revert to 21.4 which I did but found I now had the exact same problem. I then removed Magisk and flashed a clean stock boot image to see if that helped - it didn't. No matter what version I try I cannot enable any modules other than systemless hosts.
I have removed Magisk and then checked the adb folder to see if there were any residual files leftover which may be causing issues but the folder was empty so I know that's not the problem. Not sure if there is anywhere else I need to check?
I have tried clean installs, dirty flashes, upgrades, downgrades all to no avail and I'm completely stumped by this behaviour. Is there anybody that may have an insight into what is causing the bootloops whenever I enable Magiskhide?
Related
Running stock 4.4.2 rooted w/xposed installer. Decided to try Wakelock Terminator to kill some wakelocks (google play services). Installed it, activated it in xposed, and ever since then my phone reboots about a minute or so after booting into Android. I disabled xposed installer in Settings -> apps and my phone ran for almost a week straight without rebooting, then just randomly this morning it rebooted and it's now boot looping again, even after uninstalling xposed framework. Not sure what to do from here. Went into TWRP and cleared cache and dalvik cache and ran fix permissions to no avail. Anyone seen this before?
Flashed xposed-disabler, still rebooting
Reflashed the ROM and it seems to be fixed....fingers crossed.
hey everyone, clean installed Artmod 10 then installed MultiROM using the app, after restoring apps/data and installing Xposed, after restarting it started crashing seconds after boot (I can see the lockscreen and unlock it) then it starts up again, tried to diagnose myself, deleted Xposed and it's the same thing.
so I uninstalled MultiROM then fresh installed Artmod 10, installed Xposed and restarted, nothing happened, installed MultiROM and restarted, again nothing happened, so I restored data/apps again, updated everything with google play, after restarting it happened again, tried deleting Xposed, same thing, any idea what's causing this?, logcat attached (after deleting Xposed)
Nevermind, I made a mistake and restored some system data
Hi,
I have been using xposed on my Galaxy S5(klte) with AICP (MM) for some time now and xposed has worked flawlessly with it. Today I tried to look something up on my phone but when I pressed the home and/or the power button the screen didn't come on. I didn't think much of it and restarted. The phone booted up but only to the screen where it says "Starting apps..." and then just didn't respond anymore. So I decided to wipe cache and system and install AICP and the newest open gapps again. That worked fine and I was able to use my phone. I then flashed xposed arm23 v87 again. After it prepared all the apps the phone stopped at "Starting apps..." again.
Can anybody tell me what I am doing wrong or what I should try next?
/edit:
After I disabled xposed (touch /data/data/de.robv.android.xposed.installer/conf/disabled) the phone boots without a problem but I would like to somehow use xposed anyway, of course
Does anybody know how I could debug this? Is there a startup-logfile for xposed? I know it worked with that exact version of that rom for three month until yesterday morning and I didn't change anything.
Ok, it was amplify. Sorry for that.
I have ZE553KL international version and install the Magisk via the boot.img method (didn't want to touch the recovery for upgrade reasons). Below is what I did after Magisk has successfully after installed:
1. I install Systemless Xposed, but give me the error "Xposed is installed, but not active".
2. After reading around on Xposed git issue, some user were having SELinux issue, so, I load the Systemless SELinux changer and change to permissive - Xposed worked after that.
3. I installed "Roaming Control" and "Smart Network" from Xposed Repo
4. After enable the Xposed module, the phone crashed on restart (would give me warning on Android UI, keyboard crash, and among others. I would stuck at unlock screen with no way of unlock the phone), I restart the phone and hit the power and volume key and it started and seems to work. Including the two Xposed module.
5. After that I enable systemless host file and install Ad-away, and some Magisk module - CloudflareDNS and Sony Music module.
6. Restart the phone, and the phone crash hard, non stop. Took me many restart and pressing the button around to get the phone started. After which I uninstall the two Xposed module, the phone still crashing. So I decide to uninstall Systemless Xposed totally.
7. After that, it seems the system is restarting normal, but still crash randomly. Decide to install Systemless Greenify, restart, phone started crash heavily like when sytemless Xposed was installed.
8. I remove the all Magisk module, thinking it would clear the systemless partition. Restart.
9. Decide to install something simple, install Magisk Cloudflare DNS module, restart phone, start crashing again.
So now, it at the point if I have any Magisk module installed, the phone would crash hard and stays at lock screen. So I enable Core mode, which pretty much is what is the same as what I can do to make the phone stable. I have attached what I can extract from the logcat, hope it will help some debugging.
[2018-07-01] Thought I would like to update. after running safely in core mode for awhile, the urge of play around on getting Xposed running came up again. I change the update channel into Beta, and Magisk Manger immediately prompt for 16.4 version available and whether I want to install it. Choose, yes, and use direct install (as it the recommended method). Quickly, it prompt for me to restart, and this is where the horror comes. After the usual warning about unlock bootloader, Asus logo then it got a new message indicate the system are corrupt, and it would restart by itself again, warning on unlock bootloader, Asus logo - froze.
- Have tried, flash back the stock boot image
- I have tried flash patched boot image via 16.0
Still not working.
Than I was forced to flash TWRP (@shakalaca, thanks you the man), pretty much defeat my purpose of keeping the original recovery of intend easier upgrade for Oreo.
- Tried to flash the original WW-71.60.139.30 rom I was on using TWRP
- Use the Magisk-uninstaller-20180627.zip
Still not working.
It was among some other useless stupid thing that I tried also didn't help, eventually I believe this two step made the phone boot again:
1) Flash the original boot.img at fastboot
2) Flash Magisk 16.0 zip file via TWRP
Wolla, phone booted, no data lost, so far all okay. Hope this may help some people.
Okay so I originally had this issue and wasn't sure what caused this so I went back to stock ROM and started from scratch. My goals are to play PokeGo with smali patcher. So everything worked fine up until I went to hide PokeGo in magisk. I rebooted and I get this upon boot and it just hangs for mins. The only mods are TWRP and Magisk. Adhell3 is separate and I just that for domain blocking
Sorry for the side ways photos I tried to fix it.