Related
These are the steps that I took to finally get systemless root and xposed. Android pay works now. I thought I would share this. It took me over 5 days of many many wipes and restores. I will also discuss some of my phone quirks in here. The reason why I am discussing these quirks is to explain that every phone is very very unique and if people do not have enough experience, they will end up with very different results
Standard disclaimer: Not responsible for anything that goes wrong with your phone
I also would consider this to be moderate difficulty, its not really for beginners due to multiple pre reqs and terminology
I would consider this very early beta at best, sometimes xposed does not stick, so far I think I finally figured out how to make it stick with every reboot.
I- My phone:
I have V10_H901_V20J_Stock_Custom_2e-signed , so obviously I had to go through the pain of understanding that thread. If your phone is already on that rom , then you must have TWRP in place by now. That of course is a prerequisite.
II- Visit the following threads, Credit goes to all the developers there, I am merely putting it as a write up.
A- This is the main thread, honestly, didn't love the instructions there, hence why I am doing this.
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
you will need to download the following from that thread ( but I put in the links to the right files)
There is no need to place in any specific folder, I usually put every thing on my external SD
1- Magisk: http://forum.xda-developers.com/devdb/project/dl/?id=19960&task=get
Place it anywhere you can easily access it.
Edit added 09/11/11: magisk controller app : http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
2- PHH systemless SU: http://forum.xda-developers.com/attachment.php?attachmentid=3847928&stc=1&d=1471642336
PHH super user app to work with systemless root :
https://play.google.com/store/apps/details?id=me.phh.superuser
B: Xposed systemless thread: here is the main thread
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
1- Download Systemless xposed: xposed-v86.5-sdk23-topjohnwu.zip form : http://forum.xda-developers.com/attachment.php?attachmentid=3847909&d=1471640756
2- download the xposed material design app to control xposed:
http://forum.xda-developers.com/devdb/project/dl/?id=19668&task=get
Steps - This is what worked best for me, I have heard numerous times on the v10 stock rom thread that our roms come in with systemless root. I can never get that to work systemless. If you know a better way, feel free to share the knowledge.
1- Back up ! use TWRP, Here is quirk number one from my very special phone: TWRP restores fail if the phone is hot. They do not restore properly. Do what you need to do to keep your phone cool if you need to restore. I have tested this about 5-8 times in the past 3 days. If my phone is pre-cooled ( use your imagination ), it restores 100 % without missing apps or errors. If it gets hot, then I get app crashes, errors, and all sorts of corruption.
2- Uninstall xposed if you have it running on your device - THIS IS A MUST make sure you use the official uninstaller that came with your xposed version
3- unroot your phone. use SuperSU app to unroot your phone: Do restore the system boot when prompted, do NOT restore original recovery, you need twrp obviously.
4- Boot into recovery manually: Now I feel like this is most confusing part about LG phones, and its never really well written:
Power down the phone
hold the volume down
with the volume down being held ( do not let go) , press the power button, until the LG logo appears, as soon as that happens, let go for 1/2 second then press the power button again ( this whole time the volume down button should be pressed ). You will get two prompts of warning, if you are successful, about the device being erased, it will not get erased You will simply just boot into TWRP
5- Flash the following in order , do not queue, TWRP is finicky at best for our phones , never queue
- Magisk from step A - 1
-phh super user A - 2
6- reboot phone. Your phone is now systemless rooted, the root can be turned on/off on demand.
You will find magisk app on your phone, do not start , it will simply crash
you will need to install the PHH super user app from step A- 2 , this is a simple apk from the play store.
then you can mess with magisk if you would like, I will explain it's options later
7- Uninstall whatever xposed controlled app you used to have, install the material design xposed app controller from B-2
8- now that you have root, reboot to recovery, using whatever app you use to simple reboot into recovery (quirk alert: I can never find a way to include reboot to recovery from the power menu, no matter what mods I have)
9- flash systemless xposed from B -1 . wipe dalvik/cache 3 x , wait for your phone for 500 years to boot up
10- you are now systemless. go into the xposed app and check all the modules to re-enable them
11- VERY VERY IMPORTANT: xposed does NOT stick with simple reboots, soft reboot, or recovery reboot.
09/25/16 : update. Xposed now trips safety net. Even if it's systemless. Some reports also say Magisk will trip it. Sorry but this guide is now obsolete.
Great guide works perfect!!!
I'm running this systemless train [powered by magisk] really smooth. I'm running rooted stock MM with no issues at all. I can reboot with G4tweakbox mod, Xposed sticks every time and is very stable.
This probably has been asked and answered a thousand times, but since we can unlock the bootloader can't we just flash TWRP after that and than do these Step?
No
johnwayne007 said:
This probably has been asked and answered a thousand times, but since we can unlock the bootloader can't we just flash TWRP after that and than do these Step?
Click to expand...
Click to collapse
Not really
Here are the problems we faced with MM onwards
1- LG disabled the flash commands with MM, even though its is an unlocked bootloader. Hence why you have other threads with instructions on how to circumvent the good old fastboot flash commands.
2- TWRP needs compatibility with the v20J update. I am not sure if we have any devs working on that
So we are in an appleisk like situation with the newest update. No dev = no further progress, unless you want to loose root and recovery . You have the wonderful people here at XDA to thank for that, who constantly b**** at developers for that.
I Have tons of bugs on marshmallow , but I refuse to update until this situation is fixed. Next phone is nexus. I am so tired of all this BS with all the other manufacturers.
jmichaels1982 said:
11- VERY VERY IMPORTANT: xposed does NOT stick with simple reboots, soft reboot, or recovery reboot.
You need to power down your phone fully. Then power up . That is my personal experience. and I have tried it over 5 times and now it sticks with every boot.
Click to expand...
Click to collapse
just wondering if you could elaborate on Xposed not "sticking"?
dimm0k said:
just wondering if you could elaborate on Xposed not "sticking"?
Click to expand...
Click to collapse
It will say in the xposed app that xposed is installed but not active.
Sent from my LG-H901 using Tapatalk
jmichaels1982 said:
It will say in the xposed app that xposed is installed but not active.
Click to expand...
Click to collapse
Are you using the layers app with hydra installed? Removing it might help you out. Once I did that I had no issues keeping Xposed to stick and may be a bug with v3
This was very well written and easy to follow. Systemless root and xposed are running perfectly! Thank you
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
apologies
Sippi4x4man said:
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
Click to expand...
Click to collapse
Sorry man , I fixed all the links.
I feel like an idiot....I've been trying this for 2 days and no success. Used KDZ to get to bone stock J build, then used the .tot updrade to get TWRP and rebooted, now I have an unrooted stock rom with twrp. I adb reboot into recovery and successfully flash magisk and then successfully flash phh superuser but after I reboot I don't have root.....Can anyone assist?
EDIT: Nevermind.....apparently I was flashing Magisk v3 and not v6...not sure how that happened. I rebooted into TWRP, flashed magisk v6 and then phh superuser and I now have root.
Thank you for the guide.
Sippi4x4man said:
Can someone provide me an alternative link for PHH systemless su? OP link not working for me
Click to expand...
Click to collapse
Trying opening the link outside of xda labs app. I loaded the link in Firefox and now it downloads properly
Can some one provide me an explanation of what it means to have a systemless setup and the benefits of that!?
I installed as you instructed and It mostly works great. Thank you. May I ask what settings you use for Viper4Android (External Speakers)? I am not sure on how to get it working. I installed the systemless version you posted. I am also using the same ROM you are. However when I enable Viper4Android, I notice no difference whatsoever in the sound of my external speakers... Just playing an mp3 via Google play music. Any info would be greatly appreciated. Thank you.
Blur
For the life of me I can not get this working with the systemless xposed installed. With just root everything is fine. As soon as I install xposed it immediately fails. I tried the newest version and the version linked in the directions. Viper also works fine. Just not xposed.
nookie1916 said:
For the life of me I can not get this working with the systemless xposed installed. With just root everything is fine. As soon as I install xposed it immediately fails. I tried the newest version and the version linked in the directions. Viper also works fine. Just not xposed.
Click to expand...
Click to collapse
OK so this is redundant,so I apologize in advance. But
1- you can not install xposed over the same version without creating problems. You can only go up in versions when installing. Not sure why but this is my personal experience.
2- when all else fails, uninstalling magisk and xposed and re install. If still fails then delete your system partition and restore an older back up (hopefully you did back up). From there repeat the process. Always start with fresh files if it pertains to your problem. Meaning, Re-download xposed systemless.
Good luck
Sent from my LG-H901 using Tapatalk
jmichaels1982 said:
OK so this is redundant,so I apologize in advance. But
1- you can not install xposed over the same version without creating problems. You can only go up in versions when installing. Not sure why but this is my personal experience.
2- when all else fails, uninstalling magisk and xposed and re install. If still fails then delete your system partition and restore an older back up (hopefully you did back up). From there repeat the process. Always start with fresh files if it pertains to your problem. Meaning, Re-download xposed systemless.
Good luck
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Actually found out Google updated safenet the other night where it stopped working with xposed installed with magisk. Without xposed everything still passes. Had to use the other method of not using magisk and using suhide and that method still works with everything.
jmichaels1982 said:
I Have tons of bugs on marshmallow , but I refuse to update until this situation is fixed. Next phone is nexus. I am so tired of all this BS with all the other manufacturers.
Click to expand...
Click to collapse
It'll have to be a Nexus 6p, or older because the Pixel phones will supposedly have locked bootloader.
Thanks for the great step-by-step directions!!! Had been reading all of these related threads trying to make sure I knew what order to do everything. Followed the steps as written. Checked when I got root, before installing xposed, and SafetyNet showed green. Installed xposed and rebooted - only issue I had here was when it finished updating apps and got back to my home screen - all of my app shortcuts on all screens were gone, including the bottom line. The widgets I had previously were still there. So it just took a few minutes to re-do all my screens - not that big a deal to get all this done!
But then I had the same problem as nookie1916, SafetyNet and Android Pay would not work now. So I tried turning off the xposed framework and rebooting, and that worked - SafetyNet showed green again and I was able to load my Chase Visa onto Android Pay. Then turned xposed back on and rebooted.
So it's not quite the way I wanted it - but I use xposed features much more than I need Android Pay.
Thanks for your help!!!!!
Hey guys,
i finally did it and rooted my device with Magisk. It was horrible to erase all of my data, even if u got a littler backup. So now Magisk and Root works great and without problems, safety pass and so on, but i want to install Xposed to for XInsta and stuff.
So i tried many explanations to get it installed, but i always get into a bootloop. I tried it to install via the Magisk Manager itself. Then with Xposed.apk installed and manually over recovery. I also did what some videos say and gave Xposed Installer.apk permissions and wiped dalvik/cache after the install of the SDK. But i can do what i want, i'll get into a bootloop.
How can that be?
Device is a normal SM-G930F with Stock Nougat 7.0 (SDK24)
you will lose safety pass
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
you need update magisk to 14.3
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
Open magisk installer > modules > + sign > locate xposed systemless.zip istall xposed-v88.2-sdk24-topjohnwu.zip
https://forum.xda-developers.com/attachment.php?attachmentid=4319004&d=1509434219
istall XposedInstaller_3.1.2_Magisk.apk
https://forum.xda-developers.com/attachment.php?attachmentid=4297539&d=1507562905
I hope I have been of help
@atarum0r0
So i would lose safety pass? Then i would not be the thing i am happy with, because i use snapchat and so on. No different ways? Didn't even know that there's a higher version of Magisk than 14.0.
CptDayDreamer said:
@atarum0r0
So i would lose safety pass? Then i would not be the thing i am happy with, because i use snapchat and so on. No different ways? Didn't even know that there's a higher version of Magisk than 14.0.
Click to expand...
Click to collapse
if you want xposed, there are no other ways, unfortunately at the moment
Magisk 14.3 is beta release
@atarum0r0
So you know that or when a fix will come for this? Or how i get known of this?
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
@atarum0r0
OK I updated Magisk to 14.3 and with the Magisk Manager I installed the Xposed Framework Systemless SDK24 and what happend? Bootloop. God damn it man.
Ok I've installed Xposed APK previously before framework, but that shouldn't do any difference. So why the hell does is not work for me? Is it because Stock ROM?
i am sorry, i have not problem and i'm using THE GALAXY PROJECT ROM https://forum.xda-developers.com/galaxy-s7/development/rom-galaxy-project-t3440314
CptDayDreamer said:
@atarum0r0
OK I updated Magisk to 14.3 and with the Magisk Manager I installed the Xposed Framework Systemless SDK24 and what happend? Bootloop. God damn it man.
Ok I've installed Xposed APK previously before framework, but that shouldn't do any difference. So why the hell does is not work for me? Is it because Stock ROM?
Click to expand...
Click to collapse
1. Install XPOSED INSTALLER FOR MAGISK . APK
2. Flash xposed through magisk manager
3. Reboot
Bootup takes some time. Also for snapchat: once you've logged in, there's no need to worry about safetynet failing to pass.
@iorpheus96
Dude i just did that. Xposed Version 3.1.2 is installed. I go into Magisk manager on downloads and select Xposed Framework (SDK 24). I press to install directly and it reboots, but will never wake up again from bootloop.
CptDayDreamer said:
@iorpheus96
Dude i just did that. Xposed Version 3.1.2 is installed. I go into Magisk manager on downloads and select Xposed Framework (SDK 24). I press to install directly and it reboots, but will never wake up again from bootloop.
Click to expand...
Click to collapse
Try wiping dalvik/cache theough TWRP and reboot
iOrpheus06 said:
Try wiping dalvik/cache theough TWRP and reboot
Click to expand...
Click to collapse
I just did that. It was also my idea and i thought maybe that would help but it didn't.
Ok i have news. The systemless does not work for me. Normal downloaded Xposed V88.2 SDK24 worked. You were right. Restart needed much time but worked. I tried Systemless again also, but after 10 minutes my S7 war thermonuclear warm but still booting. I surrendert systemless. The only advantage is, that updates still work or what?
It there a way to install xposed and pass safetynet?
Some guides say it wont pass and most don't even mention it.
There are no known methods to get xposed to pass safetynet while it's enabled. It's simply too invasive and detectable.
Your options are to use an app like xposed switch to turn it off when you need safetynet, or if using the magisk module, disable the module when you need safetynet.
For snapchat you can login with xposed disabled, then turn it on after logged in, and it will continue to work.
Beanvee7 said:
There are no known methods to get xposed to pass safetynet while it's enabled. It's simply too invasive and detectable.
Your options are to use an app like xposed switch to turn it off when you need safetynet, or if using the magisk module, disable the module when you need safetynet.
For snapchat you can login with xposed disabled, then turn it on after logged in, and it will continue to work.
Click to expand...
Click to collapse
Thanks for the answer.
I don't have snapchat so that won't be a problem.
Any other apps that I have to apply this process? Like Android Pay for example? I use that often.
Android pay would probably need you to turn it off.
I have heard that some apps don't actually require SafetyNet to pass in its entirety, only that some aspects have to pass, which Magisk hide can do with Xposed on. But I think Android pay needs a full pass, which can't happen with Xposed on.
That's a bummer. Seems I won't install xposed then :/
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
I have rarely had any bootloop on my previous devices, so I'm not sure if this even counts as bootloop:
An hour ago I found my Pixel 2 (stock 8.1, Magisk 14.5 unmodified, TWRP 3.1.1) restarted itself (with the internal error message it's hard to miss). So I hit OK and enter the pattern to unlock. Upon unlock it reboots and arrives at lock screen again. Another unlock would trigger another reboot, over and over.
Luckily, I had Magisk uninstaller stored on SD card so I went in recovery to flash that, which seems to have restored the backed up boot image, and the phone is properly functional again. Then I flashed Magisk and it's all fine now.
I'm not attributing this issue to Magisk but just wonder if anyone else has seen this issue before. With lock screen being properly loaded, I'm not sure if this even counts as a bootloop.
Another factor to consider is, about two hours before all this happened, I installed AdAway to modify the host file. Don't know if that could be the reason, but now I've modified the host file again, will see if this issue comes back.
I just started having the same problem about the same time. I did a complete shutdown from the lock screen and when it fully booted, it was fine overnight, but it started acting up again this morning, so I did a complete shutdown again. It hung on the shutdown screen, so I had to do the hard reboot. Doing fine again, for now. I also have Magisk and AdAway, but I'd had both of those active for a few days before this started up.
I has something similar but different happen. After updating to 8.1 with magisk, I updated my hosts with adaway. I then had it hang on shutdown (this was the first time this had happened). Hard reset and rebooted and everything seemed to be fine. I then put it on the charger overnight, only to wake up the next morning and find it in the recovery menu saying there was an error booting the system and recommending a factory reset. I ignored that and rebooted, and haven't had any other issues since, but that one was weird.
It's something to do with magisk 14.5 456 beta. I've had the same boot loops, reverted to stock boot.img and problems went away
I haven't has this issue since I posted. To be clear, the problem I had could not be solved by a hard reset - it actually reboots itself every time I try to get past the lock screen for the first time after the previous (self) reboot. It's exactly a bootloop except that the phone makes it into the OS instead of failing to boot.
It can be Magisk or Adaway, no worries. I just pray it's not a hardware issue.
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
I'm still using Magisk 14.3 on 8.1, "Flash" kernel, no issues.
I've not had this issue since I posted about it. I uninstalled one live wallpaper app, which I'm not sure did the trick or not.
froader said:
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
Click to expand...
Click to collapse
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
cswithxda said:
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
Click to expand...
Click to collapse
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
froader said:
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
Click to expand...
Click to collapse
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
cswithxda said:
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
Click to expand...
Click to collapse
Thanks for confirming. I wasn't sure if that was present flashing via TWRP, but makes sense that it would.
Same exact "Internal error" warning and occasional boot loop after upgrading the Pixel 2 (not XL) to 8.1 from Magisk 14.5.1456 using TWRP 3.2.1.0. Also an AdAway user. Glad to hear I didn't mess it up and it's just a quirk of the method and the alpha/beta stages. Hopefully this resolves soon as I hate guessing whether my device will go belly up at random. Seems like Flash kernel with Magisk 14.3 may be ideal - any other confirmations that this is a stable method?
I'm having this same issue as well! Using Magisk 14.5 1456, with the latest TWRP non-beta, and the Unified Hosts Adblock module. Randomly my phone goes into a soft reboot loop like your describing. If I hard reboot using power + volume up it seems to fix it for a time, then it happens again at a, seemingly, random time. It's crazily frustrating. The only other things I have that involve root are a terminal app, Drives roid, and CoSy to sync Facebook contacts. I also had Substratum using the root method, but I uninstalled that today wondering if that was the cause.
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
cswithxda said:
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
Click to expand...
Click to collapse
Were you able to recover from the bootloop at all without uninstalling? For me I was able to force restart it, it would be fine for a few hours then it would bootloop again.
Additionally, I uninstalled Magisk and flashed the stock boot image as well and so far it hasn't come back. I still have TWRP.
Not at all, hard reset still sees the same reboots over and over, so I had to try something. And the only thing I found was the Magisk uninstaller on the SD card lol. I then uninstalled the Magisk and reinstalled it, and the issue has not come back so far.
I'm having that boot loop. I'll try uninstalling magisk
Sent from my [device_name] using XDA-Developers Legacy app
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Interesting about removing AdAway. I had a hosts adblocker as well, I wonder if that has something to do with it.
So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant
Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.
I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.
There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.
BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.
I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process
Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...
If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.
Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.
Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.
I dont have any issues with safetynet.