Lenovo p2 with android 7
Magisk 25.2
Everything works fine until I turn Zygisk on. Then, when I reboot my phone, magisk goes back to N/A. Tried to wipe data and root again, the problem persists.
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..
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.
Hi, I wanted to try the debloater module, so i installed it on my Oneplus 7 Pro. After the installisation and reboot, the device always stayed on the bootlocker warning screen really long. After that it always startet to fastboot.
My first try was to flash the module uninstaller: https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242.
-> Flash was sucessfull, but it did not work at all.
Second try was to delete the modules via TWRP File explorer, so i deleted the folder of the module.
-> Still same problem, boots from bootloader unlocked warning screen directly to fastboot.
My next try was to flash the magisk uninstaller.
-> Flash sucessful, phone running again.
After that i reflashed magisk.
-> Problem started again.
Next step was flashing the uninstaller and then booting to android, to delete the magisk Manager. After that reflashing magisk.
->Same Problem as in the beginning. But there is no module when i have a look at /data/adb
Right now my device is running, but i have no idea how to reinstall magisk. Is there anybody who could help me?
I'd like to get magisk back and would prefer not to factory reset or wipe any sd data...
If there are no modules installed, there's likely something else going on...
Examples of things to do/try:
Don't install TWRP. Leave the boot image untouched and just boot TWRP to install Magisk (there's been instances where Magisk and TWRP conflict).
Reflash just the system images and leave data untouched.
Ask for advice in your device's forum. That's usually where you'll get the best device specific help.
Thank you for the advice!
So you mean i should flash the stock recovery again? And then sideload TWRP, or simply patch my boot image and flash it via ADB?
But why did i not have any problem with TWRP and magisk all the time before? Everything startet with the reboot after installing a new module?
I will also post my question in the OP 7 Pro forum!
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
GeekMcLeod said:
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
Click to expand...
Click to collapse
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
I just wanted to debloat the oneplus galerie, so i could install an older version from apk mirror, that still has the never settle stamp.
6nchris said:
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
Click to expand...
Click to collapse
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
GeekMcLeod said:
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
Click to expand...
Click to collapse
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
i came from 3T to the essential phone. I Think modding the OP 3T or the OP 7Pro is much easier than the essential PH1...
6nchris said:
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
Click to expand...
Click to collapse
Ahh, sad too say but I can't help with that. I don't take calls often so never noticed anything like that.
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?
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'?