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.
Related
after installing the xposed framework i was stuck in a bootloop,
the safemode saved me, it worked and now i booted successfully into android.
do i have to delete or deinstall now something before i reboot the device again?
schlunk said:
after installing the xposed framework i was stuck in a bootloop,
the safemode saved me, it worked and now i booted successfully into android.
do i have to delete or deinstall now something before i reboot the device again?
Click to expand...
Click to collapse
You carefully avoided to mention any detail, so I can't help with the bootloop.
If you want to remove Xposed completely, press the "uninstall" button in the app, then uninstall the Xposed Installer app and any modules.
sry,
i am on an alcatel 6012d
android 4.2.2 kernel 3.4.5
after installing couldnt get pass the logo.
i did a cache & data swipe in the boot recovery via vol+ power.
after that the xposed safemode still worked and it finally booted.
do i have a clean factory android now or are there some files left?
i dont see xposed in the applications anymore.
btw. no idea if i did something wrong when installing, but with the phone xposed doesnt work it seems..
My phone just told me that a new version of the Xposed Framework was available and I chose to update it. It asked me to reboot, but this fails as the boot never completes. The OnePlus is stuck on the rotating logo.
I seem to remember that there is a chance that I can interact with the phone during boot to abort the loading of the Xposed Framework. Do I remember correctly or is the only solution now a full phone reset?
Googled a solution: Press power button repeatably during boot disables Xposed Framework. Phone has booted. Now I to find out how to make Xposed load properly...
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?
Hi ereyone.So I have this problem:I have Exynos model and had it magisk rooted by patching AP firmware file via Magisk Manager(with keep force encryption check box checked) and then flashing it with the rest of the files in Odin + modules like Riru,LSPosed,Smali patch,Android Core Patch&Magisk app hidden. Long story short-I used this setup for more than 2 years ang gathered decent amaount of life in it(Photos,Videos,Apps and ect.)One day while traveling from point A to point B I noticed I mighgt not make it back home until phone dies so I enabled extreme power saving on it and thought I did managed to get back home without it dying price I had to pay for it was not worth it. For the first time in I my whole life expierence using Note after switching phone from yet another extreme power saving to High efficiency(Note: not first time I did this switch between these two modes, happens rarely but definetily wasn't the 1st time with this setup) the previous hiden Magisk app first gave me update notification that I pressed(thought nothing hapened) and then it started crashing whenever you wanted to open it or it had to show toast for app wether the app was or was not granted su permission, it still was giving root permission to apps and Magisk hide seemed to be working but opening Magisk manager was out of the question.while Magisk hide worked for first few restarts due to riru module, even once in between to restarts I had LSPosed to open up too ,but only that once, at some point Magisk hide stoped working and I needed to add new app anyway so Update was inevitable like Thanos. So I downloaded firmware files that matched the currectly installed one,patched AP with newly downloaded and installed Magisk manager that for some reason never sees already installed Su permission, loaded it with the rest files in Odin and was sure to choose CSC not HOME_CSC which tells odin to do wipe before flashing and thought Odin didn't say anything about wiping before flashing after flashing Odin gave PASS and phone reboot first it showed me android mascot with spinning circkle animation and bar below it from 0 to 100% and after that it restarted again and booted for about Half an hour after to my demise I was greeted with Setup screen and obvious data vipe during mascot boot part, I panicangly double cheked Odin screen and it did say I choose CSC not HOME variant.So My question is: Do I not know how perform update type flash like Smart Switch do or are there some ohter steps I'm missing like a complete idiot, Please someone if you know how explain because this makes me weak and I think I'm at my fcking limit.
P.S My only hope seems to make a nand backup but how do I restore it and will it not break my Stock+Magisk installation?
As many of us on A12 are finding out, the only way we can boot either into recovery or boot into Magisk Rooted is by using a USB cable. However, when I installed LSPosed, the software applied settings and rebooted into root mode. That suggests there is such a way possible.
Does anyone know if there's a module that will offer shutdown options to include "boot to recovery / reboot to root / reboot without root'?